Permission Catalog Reference

Stable permission keys used to build SteelEngine roles.

The Permission Catalog is the vocabulary used by seeded and custom roles. Keys are stable identifiers in family:action form. The Roles editor groups them by resource family and displays a plain-language description for each permission.

Workspace collections

AreaReadCreateUpdateDelete or manage
Workspaceworkspace:readworkspace:createworkspace:updateworkspace:delete
Membersworkspace:read_members——workspace:manage_members
Settings———workspace:manage_settings
Source Control———workspace:manage_source_control
Documentsworkspace:read_documentsworkspace:create_documentsworkspace:update_documentsworkspace:delete_documents
Foldersworkspace:read_foldersworkspace:create_foldersworkspace:update_foldersworkspace:delete_folders
Workflow foldersworkspace:read_workflow_foldersworkspace:create_workflow_foldersworkspace:update_workflow_foldersworkspace:delete_workflow_folders
Chatsworkspace:read_chats—workspace:update_chats—
Inboxworkspace:read_inbox——workspace:manage_inbox
Notificationsworkspace:read_notificationsworkspace:create_notificationsworkspace:update_notificationsworkspace:delete_notifications
Credentials area———workspace:manage_credentials
Custom integrations area———workspace:manage_integration_apps
MCP areaworkspace:read_mcp——workspace:manage_mcp
Appsworkspace:read_appsworkspace:create_appsworkspace:update_appsworkspace:delete_apps, workspace:publish_apps
Jobsworkspace:read_jobsworkspace:create_jobsworkspace:update_jobsworkspace:delete_jobs
Environmentworkspace:read_environment——workspace:read_environment_values, workspace:manage_environment, workspace:manage_byok
Workload provider configurationworkspace:read_byokworkspace:set_byokworkspace:delete_byokNarrow metadata, write-only set/replace, and cleanup actions; no secret read
Memoryworkspace:read_memory——workspace:manage_memory
Logsworkspace:read_logs———
A2Aworkspace:read_a2aworkspace:create_a2aworkspace:update_a2aworkspace:delete_a2a, workspace:publish_a2a
Promotion———workspace:promotion_manage, workspace:promotion_export, workspace:promotion_apply, workspace:promotion_activate, workspace:promotion_attest

Workspace source control

Manage source control (workspace:manage_source_control) lets a custom role manage a workspace's repository, branch, package, branch lock, editing and deployment policies, resource assignments, and approved-package synchronization/deployment. Assign it at the intended workspace scope and include workspace read access. Effective Manage settings (workspace:manage_settings) also provides this connection authority, as held by workspace and organization administrators.

This narrower grant does not authorize organization GitHub App setup, access to another organization's workspace or credentials, or unrestricted workflow editing. Authoring a workspace capture still requires settings administration and read access to every included workflow. See Branch-connected workspaces.

Workflows and knowledge

FamilyPermission keys
Workflowworkflow:read, workflow:create, workflow:update, workflow:delete, workflow:execute, workflow:deploy, workflow:manage_public_api, workflow:publish_mcp_tool
Knowledge baseknowledge_base:read, knowledge_base:search, knowledge_base:create, knowledge_base:update, knowledge_base:delete, knowledge_base:restore
Connector configurationknowledge_base:read_connectors, knowledge_base:create_connectors, knowledge_base:update_connectors, knowledge_base:delete_connectors; workspace-local binding also requires credential:use
Knowledge documentdocument:read, document:create, document:update, document:delete, document:sync
Search chunkchunk:search

Data

FamilyPermission keys
Databasedatabase:read, database:query, database:create, database:update, database:delete
Tabletable:read, table:query, table:create, table:update, table:delete, table:manage_schema, table:import, table:export

database:delete authorizes deletion of an empty database through the dashboard. It does not expose database deletion to Chat, MCP, scheduled Sub Agents, workflow tools, or API-key clients.

Credentials, keys, MCP, tools, and skills

FamilyPermission keys
Credentialcredential:read, credential:use, credential:share, credential:manage, credential:delete
Integration appintegration_app:read, integration_app:use, integration_app:connect, integration_app:share, integration_app:manage, integration_app:delete
Credential setcredential_set:read, credential_set:list, credential_set:create, credential_set:manage
API keyapi_key:read, api_key:read_workspace, api_key:create, api_key:update, api_key:revoke, api_key:revoke_workspace, api_key:use
MCP servermcp_server:read, mcp_server:manage, mcp_server:refresh, mcp_server:delete
Workflow MCP serverworkflow_mcp_server:read, workflow_mcp_server:manage
MCP tool and scopemcp_tool:list, mcp_tool:call, mcp_scope:use
Built-in tooltool:read, tool:use, tool:administer
Custom toolcustom_tool:read, custom_tool:use, custom_tool:create, custom_tool:update, custom_tool:delete
Skillskill:read, skill:use, skill:create, skill:update, skill:delete

Custom app permissions apply to the app registration. Connection credentials retain their own access checks. workspace:manage_integration_apps requires an admin-level API-key scope when a key is used. See Custom Apps.

Organization and billing

FamilyPermission keys
Organizationorganization:read, organization:update, organization:manage_members, organization:manage_authz, organization:manage_models, organization:manage_api_keys, organization:manage_workload_identities, organization:manage_byok, organization:administer, organization:promotion_repository_configure, organization:promotion_configure, organization:promotion_break_glass
Caller-owned personal dataorganization:read_personal_data, organization:read_personal_secrets, organization:manage_personal_data
Plan accountplan_account:read, plan_account:manage_billing, plan_account:change_plan, plan_account:manage_seats, plan_account:view_enterprise_audit

Workload identity permissions

organization:manage_workload_identities lets a signed-in human manage approved deployment applications and scoped grants. It does not permit an application or API-key caller to manage those bindings. Organization-wide automatic actions also require administrative delegation authority.

Workload identities support a closed set of existing catalog keys, rather than the entire catalog on this page. See the exact workload action and operation matrix. An automatic workspace policy grants selected actions to current and future active workspaces in the bound organization, with absolute exclusions; it does not add workspace:create or organization administration.

Promotion permissions

The promotion_* keys govern environment promotion. Promotion exports signed release bundles from one installation and applies them on another. organization:promotion_repository_configure controls the organization release repository, upstream branches, environment mapping, and workspace mappings; it requires an organization-scoped grant and read access to the managed workspaces. Organization admins have this authority by default, and custom roles can receive it explicitly. Authorizing automatic deployment also requires promotion management, apply, and activation access. organization:promotion_configure separately sets the promotion policy and signing trust; it does not grant repository configuration. organization:promotion_break_glass authorizes an audited temporary unlock. The workspace keys cover enrollment, export, import and apply, activation and rollback, and review evidence.

The seeded Workspace Admin role holds every workspace promotion permission except workspace:promotion_attest. When a request uses an API key, every promotion_* action needs a key scope at the admin level.

Target patterns

The same action can apply to different target shapes:

  • Collection creation uses a parent target, such as workspace:<id>:documents or workspace:<id>:workflow:*.
  • Existing-resource actions use the resource, such as workflow:<id> or table:<id>.
  • Workspace subareas use collection keys, such as workspace:<id>:folders.
  • Organization governance uses keys such as org:<id>:members and org:<id>:authorization.

You choose the named permission in the UI. SteelEngine builds and evaluates the target pattern for the assignment scope.

Entitlement-aware permissions

Some catalog entries also require a plan or entitlement. Notable examples include organization authorization management, organization API keys, BYOK, seat management, and enterprise audit access. A role grant does not bypass those product requirements.

On this page