Full access to all features and settings. Cannot be restricted.
Member
Read access to most features, manage access to environment variables, LLM connections, and Studio projects. Cannot modify organization or default settings.
Manage billing, plans, and organization configuration
studio_projects
Manage
Manage
Manage / No access
Create and edit projects in Studio
When creating a custom role, most features can be set to Manage, Read, or No access. However, environment_variables, llm_connections, default_settings, organization_settings, and studio_projects only support Manage or No access — there is no read-only option for these features.
To deploy an automation from a GitHub repository, a user needs:
crews_dashboards: at least Read — required to access the automations dashboard where deployments are created
Git repository access (if entity-level RBAC for Git repositories is enabled): the user’s role must be granted access to the specific Git repository via entity-level permissions
studio_projects: Manage — if building the crew in Studio before deploying
Automations support visibility settings that restrict access by user or role. This is useful for:
Keeping sensitive or experimental automations private
Managing visibility across large teams or external collaborators
Testing automations in isolated contexts
Deployments can be configured as private, meaning only whitelisted users and roles will be able to interact with them.You can configure automation‑level access control in Automation → Settings → Visibility tab.
1
Open Visibility tab
Navigate to Automation → Settings → Visibility.
2
Set visibility
Choose Private to restrict access. The organization owner always
retains access.
3
Whitelist access
Add specific users and roles allowed to view, run, and access
logs/metrics/settings.
4
Save and verify
Save changes, then confirm that non‑whitelisted users cannot view or run the
automation.
