Appearance
Audit Log, Tenants & Organization
Audit log
Admin → Audit log is the compliance view over everything that happens in the platform:

- Summary cards — total events, access denials, role changes, most active user.
- Tabs — filter by domain: Entities, Blueprints, Actions, Integrations, RBAC.
- Each event records the blueprint/entity, date, source (UI, entity-service, integration…), operation, type and status — including denied attempts.
- Export the current view as CSV or JSON for external reporting.
Every entity also has its own Audit Log tab on its detail page, scoped to that entity.
Actions tab — workflow runs
The Actions tab is the audit trail of your workflows. Every run leaves one row per lifecycle event, and changes to a workflow definition land here too:

| Column | What it shows |
|---|---|
| Workflow | Title and identifier of the workflow; click it to open the workflow's run history. |
| Run | The run id — a link to the run details page. Empty for definition changes. |
| Entity | The catalog entity the run was started on (blueprint / identifier), when the workflow is entity-scoped. |
| Source | Who triggered the event: the user for a start or cancel, workflow-engine for completions. |
| Operation | Started when a run is created, Completed when all steps are terminal, Cancelled when someone stops it — plus Created / Updated / Deleted for the definition. |
| Status | Success or Failure. A Completed row is Failure when any step failed or timed out. |
| Details | The failing step and its error, or the run's final status label. |
Expand a Started row to see the inputs the run was submitted with. The Run ID, Blueprint, Entity, Operation and Status filters all apply to this tab, so "every failed run of deploy-service on orders-service this month" is one filter away — and Export gives you the same rows as CSV/JSON.
Tenants
Admin → Tenants manages environments:

- Every organization starts with a Default tenant.
- Create Tenant adds an isolated environment (e.g.
staging,production): separate entities, catalog pages and role assignments, switched via the tenant picker in the header. - Blueprints and entities are scoped to (organization, tenant) — the same identifier can exist in two tenants independently.
- A new tenant is not empty: it is seeded with the system blueprints (
_user,_team, …) and every existing member and organization-wide team is synced into its catalog right away, so role assignments, team ownership and team-based form rules work there without re-inviting anyone. This runs in the background just after the tenant is created — allow a few seconds before the entities show up.
Organization settings
Admin → Organization settings:

- Organization Title — display name in the header.
- URL Slug — the organization's unique identifier used in URLs.
- Logo URL — custom logo, previewed for light and dark themes.
