Skip to content
34Five.ai / Documentation
Open Studio ↗
Documentation

Find an answer

Browse popular starting points

DocumentationSecurity and Access
Security and Access

Roles and Permissions

Distinguish workspace membership, human roles, and external credentials.

Studio / MCP v1Reviewed 2026-10-24
Documentation previewDraft content · Staging instructions · Not approved for production
On this pageWorkspace membershipAn agent's roleChanging accessKeep three concepts separateNext steps

Workspace membership #

Your identity can belong to more than one workspace. Membership in the intended workspace and its assigned role determine which Studio resources you can use.

An agent's role #

An OAuth connection acts through the authorized membership. An API key acts through the role selected at creation, subject to the creator's continuing eligibility. Neither connection grants access merely because an agent asks for it.

Changing access #

Use your organization's administration process to change membership or roles. Revoke credentials that are no longer needed. After changing a connection, verify the resulting workspace and role with 34five_whoami.

Keep three concepts separate #

  • A Studio role governs access.
  • An Aura™'s Job Function describes their working responsibilities.
  • An application's connection scope describes who holds its credential.

Next steps #

See API Keys and Security and Data Handling before granting a client access to workspace data.

34Five DocumentationPrivacyContent 2b5e203ea2