Connected apps, custom integrations, and MCP servers do not use credits. Credits pay only for the built-in research tools. See What Squad costs and what uses credits.
Before you start
- Your subscription must be active. If it is not, Squad refuses the connection with the message “Your subscription isn’t active. Resubscribe to manage integrations.”
- Have the sign-in details for the app account that you want your agents to use.
Open the Integrations screen
Use one of these paths:- Click the grid icon (tooltip Integrations) in the strip at the bottom of the sidebar.
- Open Settings from the user menu in the top bar, then click Integrations under CONNECTIONS.
Connect an app
1
Add an integration
On the Connected apps tab, click + Add integration.
2
Find the app
Scroll the categories, or type in Search the catalog….
3
Open the Connect window
Click the app. The Connect window for the app opens.
4
Choose the access level
Under Default scope, select the access level for your agents. The recommended level is already selected.
5
Choose who may use it
If your workspace has teammates, the window also shows Share this account with everyone in this workspace. It is ticked for the owner and clear for a teammate. Leave it ticked to let agents use the account for anyone’s requests. Clear it to keep the account for your own requests. See Who can use an account.
6
Start the sign-in
Click Connect followed by the app name, for example Connect Gmail.
7
Approve access
In the new browser tab, sign in to the app and approve access.
8
Return to Squad
Go back to the Squad tab.
Check that it works
- The app shows under YOUR CONNECTIONS, with the account name and a scope chip that shows the access level.
- In the catalog, the app card shows Connected.
- After an agent uses the account, the row shows when it was last used.
Choose an access level
The app’s own sign-in page asks you to give full access. Squad does not narrow that access at the app. Instead, Squad checks every call that an agent makes and refuses any action that is outside the level you chose.- Most apps offer Read-only, Read + write, and Full access. Some apps use their own labels, for example Read + send for Gmail and Read + post for LinkedIn.
- Some apps have only one level, Default (“Standard access.”).
- The recommended level is not always the highest. For example, Gmail recommends Full access, and Google Analytics recommends Read-only.
- On YOUR CONNECTIONS, click the scope chip on the account row. You can also click the ⋯ menu on the row and click Manage scope.
- Under Default scope, select a different level.
- Click Save access.
Limit a single agent
By default, every agent uses the level of the account. You can narrow the level for one agent, or block one agent from the account.1
Open the account scope
On YOUR CONNECTIONS, click the scope chip on the account row.
2
Find the agent
Under Per-agent access, find the agent.
3
Choose the agent's level
In the agent’s list, select one option:
- Default (the account’s level, shown in parentheses)
- a lower level
- No access
4
Save
Click Save access.
Connect more than one account
You can connect several accounts of the same app, for example two Gmail inboxes.- On YOUR CONNECTIONS, click + Account on the app row.
- Choose the access level for the new account. If your workspace has teammates, also choose whether to tick Share this account with everyone in this workspace.
- Click Connect followed by the app name, and sign in with the other account.
Disconnect asks you to confirm. The first click changes the menu item to Really disconnect? Your agents lose access to and the app name. Click it again to disconnect. To use the account again, you connect it again.
Who can use an account
Each connected account belongs to the person who connected it: you, or a teammate. That person decides who else may use it. This matters only when you have teammates. See Invite teammates to your workspace. Each account row shows one of two tags:
To change it, click ⋯ on the account row, then click Share with the whole workspace or Stop sharing this account. Only the person who connected the account can change it. You and your Administrators cannot share a teammate’s account or make it private, and the menu shows these items only on your own accounts. You and the Administrators who can see every agent keep Disconnect, Make primary, Rename, and Manage scope on every account.
When you connect a new account in a workspace that has teammates, the dialog shows the box Share this account with everyone in this workspace. The box is ticked for the owner and not ticked for a teammate. When it is ticked, agents can use the account for anyone’s requests. When it is clear, only your own requests can use it. Reconnect keeps the account’s sharing.
In the dashboard, a connect card in chat shows the same box, with the same default. When the box is ticked, the card says “Agents can use it for anyone’s requests. You can stop sharing it later from its menu in Integrations.” When it is clear, it says “Only your own requests can use it. You can share it later from its menu in Integrations.” A card for a connection that expired shows no box. Its repair is on Integrations.
On Squad for Mac (private beta), the connect card does not show the box. An account that you connect there is private. To share it, click ⋯ on its row in Integrations, then Share with the whole workspace.
A workspace has teammates once someone accepted an invite. An open invite does not count.
An account that a teammate connected shows “Connected by” and the teammate’s name on its row, also for that teammate. An account that the owner connected shows no name.
How agents pick an account:
- An agent works for the people whose messages it is answering, or for the person who started or reassigned a mission. Heartbeats, email, and messages from Telegram, Discord, or Slack count as work for you. A scheduled task uses the accounts that its Accounts it can use setting allows. See Choose the accounts of a scheduled task.
- It uses only an account that each of those people may use. In a chat where you and a teammate both write, the agent can use your private account when it answers you, and not when it answers the teammate.
- When an agent does not pick an account, it uses the people’s own account first, then a shared account. Within each group, the account marked ★ PRIMARY comes first.
- When no account of the app may be used, the agent tells the person whose account exists and what fixes it. They can connect their own account on the Integrations page, or the account’s owner can share it.
- A teammate’s YOUR CONNECTIONS list shows only their own accounts. A Collaborator or an Administrator connects their own accounts in the same way as you.
- Accounts that other people shared show in a separate list, SHARED WITH YOUR SQUAD, with “Shared by” and the person’s name. A teammate cannot change these accounts.
- Only you and the Administrators who can see every agent see every account in the workspace. An Administrator limited to some agents sees their own accounts and, like other teammates, the accounts shared with the squad.
- Only you and your Administrators see the Custom integrations tab. Only you and the Administrators who can see every agent can change it.
- A Viewer cannot connect apps. The screen says “Your access is view-only, so you cannot connect apps here. Anything shared with the squad is listed below.”
Recommended apps
The Recommended category is first in the catalog. These apps connect in a different way from the other apps. They do not use access levels.
What protects your money in these apps:
- SiteGPT: Squad removes no tools.
- Revid: agents never get the tool that buys credit packs. Squad removes it.
- PostSyncer: agents never get the tool that deletes a connected social account. Squad removes it.
- Bazzly: Squad removes no tools. The protection is the key. A key that you create without the top-ups scope cannot spend money. If the key has top-ups on, Squad has no other control that stops spending.
Troubleshooting
Nothing happens when you click Connect. Cause: the browser blocked the new tab. Fix: allow pop-ups for the Squad dashboard, then click Connect again. The message “Your subscription isn’t active. Resubscribe to manage integrations.” shows. Cause: the subscription is canceled, paused, or past due. Fix: renew the subscription in Settings > Billing. See Manage your subscription, credits, and workspace data. An agent says an action is not allowed on the account. Cause: the action is outside the account level or the agent’s level. Fix: raise the level with Manage scope, or change the agent’s line under Per-agent access. An agent says that no account of an app can be used for a teammate. Cause: the app accounts in the workspace are private to someone else. Fix: a Collaborator or an Administrator connects their own account, or the account’s owner clicks ⋯ on the account row and Share with the whole workspace. See Who can use an account. A scheduled task says that no account of an app can be used. Cause: the task uses only the accounts shared with everyone, and the account is private. Fix: the person who connected the account shares it, or that person saves the task with Shared accounts and my own accounts. See Choose the accounts of a scheduled task. An agent says the connection expired. Cause: the app ended the sign-in. Fix: click ⋯ on the account row, click Reconnect, and sign in again. Two accounts show the same name. Cause: the app did not send an account name, so both rows get the same name with a number after it. Fix: click ⋯ and Rename on each row. YOUR CONNECTIONS shows “No connections yet”. Cause: no app is connected. Recommended apps do not show here. They show on the Custom integrations tab. Fix: click + Add integration and connect an app.Other messages
For Recommended apps, the app’s window can show:
When an agent is refused an action, it gets one of these messages and tells you:
- “This action is not allowed on this account. The connection is set to “[level]” which does not include [action].” Raise the account level with Manage scope.
- “Your agent policy restricts you to “[level]” access on this account, which does not include [action].” Change that agent’s line under Per-agent access.