Audit & roles
The Audit timeline is an append-only record of every change in the workspace — who did what, from which source, against which agent, and when. It’s filterable by source, actor, agent, and time, and exportable as JSON. Because agent changes are pull requests and runs are recorded, the audit trail answers “what changed and who changed it” without reconstructing it after the fact.
Workspace membership has three roles, enforced at the API layer:
| Role | Can do |
|---|---|
| Admin | Manage members, settings, and connections; everything operators can do. |
| Operator | Author, run, and improve agents; authorize their own connections. |
| Viewer | Read agents, runs, and dashboards. |
Manage members and their roles under Settings → Members. Workspace admins can open a member detail view to inspect connections, automations, and runs before offboarding someone.
Instance admins
Section titled “Instance admins”Above workspace roles, instance admins are bootstrapped from
INSTANCE_ADMIN_EMAILS at deploy time. An instance admin can:
- Set the instance name and branding (top-level Settings)
- Create workspaces (only instance admins see “Create workspace”)
- Access any workspace they’re a member of with their assigned workspace role
Everyone else joins via workspace invitation. On a fresh instance, the first
person to sign in with an email listed in INSTANCE_ADMIN_EMAILS becomes an
instance admin and can create the first workspace. See
Setup checklist for the bootstrap checklist.