Automo.ai

Scopes and permissions: Automo developers

Every permission an assistant can ask for on Automo, which ones a workspace starts with, and which tools each one unlocks.

Deze referentie wordt in het Engels gepubliceerd.

Lezen als Markdown

A token can only do what three things allow at once: the scopes the person ticked when they connected, what their own role in the workspace allows, and what the workspace admin has switched on for assistants in Settings, Claude Connector. Any of the three can narrow it; nothing widens it.

How a permission is granted

  1. Ask for scopes in the scope parameter of the authorize request (space separated). Ask only for what you use.
  2. The person sees each permission as a checkbox and can untick any of them.
  3. The workspace's admin policy narrows the result. Most powerful permissions start off and stay off until an admin turns them on, for every connection at once.
  4. If a tool needs a permission the token lacks, the call is refused with 403 and, where a reconnect could add it, a WWW-Authenticate: Bearer error="insufficient_scope" challenge naming the scope.

Every scope

ScopeAllowsNew workspacesTools

Protocol scopes

  • openid, email, profile: who connected (returned by /oauth/userinfo).
  • offline_access: a refresh token, so the connection survives the access token expiring.