Connections, not apps
Ando gives you a connection for each account you link, not one switch per app. One app, such as Linear, can have several connections used in different ways by different people and agents. For every connection, you decide:- Which agents can use it: every agent in the workspace, or only the agents you let in.
- Who it acts as: Ando’s own app, the member who signed in, or you.
- What it can reach: the tools, resources, and provider permissions available through that account.
Choose who can use it
The rule of thumb: shared system and company data → every agent. Your
account and your data → only the agents you let in.
Studio → Apps lists each connected app once and says who agents act as:
Connected as Ando, as a member, or as you.
The same app can have both. Your company GitHub can be connected for every
agent, while your own GitHub account is a personal account only your chosen
agents use. Add yours from the Personal account row on the app’s page.
A connection for every agent does not give every agent every action: its
tool and resource limits still apply.
Use a personal account with an agent
Only you can enable your personal account on an agent, from the agent’s Apps tab. Everything the agent does through it appears as you, so you also choose who it acts for:- Only when I ask (the default): the agent uses your account for your own requests and for scheduled runs of agents you own. Teammates’ requests cannot use it.
- Anyone who asks: the agent acts as you for anyone allowed to talk to it. Use this for an account meant to serve the team, such as a bot account.
ando up on a server, choose the folders and the agents, and
each agent gets one tool: start a task there. See
Claude Code and Codex.
Permission layers
Who can use a connection is only one layer. An agent can act only when every layer allows it.- Provider permissions are what the account granted when you connected it. Ando cannot reach beyond them.
- Agents decide who can use the connection. A personal account must be enabled on each agent that should use it.
- Tools are actions, such as searching GitHub or creating a Linear issue. A disabled tool cannot be used through that connection.
- Resources narrow where tools can act, when the app supports it. For example, a GitHub connection can be limited to selected repositories.
Our reasoning
See how Linear, Notion, GitHub, HubSpot, Granola, and Sentry map into the
connection model.