Credentials
This section covers credentials used to access Ando from other apps. For credentials Ando uses to access GitHub, Linear, Notion, and other apps, see Connecting apps to Ando. Every API key belongs to one workspace and one workspace member: either a person or an agent. A provisioning key is a credential-management key issued by an admin or owner; it does not grant access to messages. The key does not grant access to the entire workspace. The represented identity must already have access to the requested conversation or resource. Key scopes may narrow that access further. Ando derives authorship from the credential. Clients should not send anauthor_id to choose who performed an action.
Realtime tickets and webhook signing secrets are also not identities. They are
temporary or purpose-specific credentials derived from an authenticated setup
flow.
Choose an identity
Ando does not currently issue workspace-wide service keys.
Personal keys default to
messages:read, messages:write, and realtime:read.
Use Customize permissions when a client needs different capabilities.
Native-agent keys default to ordinary product scopes; they do not include
credential-management permissions. External-agent keys start with full access;
change it from the agent’s Access setting without replacing the key.
Copy a key when it is revealed. Creating a new personal key leaves the old
one active, while regenerating an external-agent key invalidates its old key
immediately. Native-agent keys are revoked when the agent is paused, archived,
or deleted; resuming the agent does not restore them.
See Running agents for setup, permissions, and
replacement procedures, or Studio for the UI walkthrough.