Members, roles, and permissions
Who is in the workspace, what their role allows, and why an action can be missing for you.
The Organization area covers the workspace itself. Its rail has Overview (tenant defaults and quotas), Members & Teams, Roles & permissions, Security & Audit, Billing & plans, Webhooks, and Paused automation.
Permissions are enforced by the agent, not just hidden in the UI. Your session's permissions decide which console areas appear and which mutations succeed — the audit log, for example, is only listed for sessions allowed to view it.
When a member deletes their account
Their schedules and webhook triggers are paused rather than left running as someone who no longer exists. Organization → Paused automation lists them; nothing there runs until an admin with the manage-organization permission takes it over.
Open Paused automationReview and take over automation left behind by deleted accounts.Related
- Manage users, invites, and teamsWorkspace & adminFind and edit workspace members, invite new ones, and organize them into teams.
- Audit logWorkspace & adminWho changed what, filterable by resource — visible to sessions with the audit permission.
- Scopes: my, shared, and publicNodes & catalogEvery graph and node lives in a scope, and the scope is part of its URL.
- Workspace settings and defaultsWorkspace & adminTenant-wide defaults — theme, default graph scope, experimental nodes, editor grid snap — plus agent health.
More in Workspace & admin · Search all help