Skip to main content
Connect an app, such as Gmail, Notion, or GitHub, and your teammates can read it and act in it for you. You connect each app once. Then you decide how much your teammates can do in it. Apps are on the Apps page in Settings. At the top, a strip says what your squad can use, for example “Your squad can use GitHub, Gmail and 6 more.”, with the number of connected apps, the number of custom integrations (for the owner and Administrators), and the main Telegram bot. An app counts only while one of its accounts works. With no app connected, it says “Your squad isn’t connected to any apps yet.” Below the strip, the switch has two views: The Telegram, Discord, and Slack bots that you chat with are on their own tabs next to Apps. Only the owner and Administrators see these tabs. See Talk to your squad from Telegram, Discord, or Slack.
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.”
  • A Viewer cannot connect apps.
  • Have the sign-in details for the app account that you want your teammates to use.

Open Apps

Use one of these:
  • Click Settings at the bottom of the sidebar, then Apps.
  • Press ⌘K (Ctrl+K on Windows) and select Apps. You can also type an app’s name, for example “Gmail”, and select it. The catalog opens with the app’s connect window.
  • While no app is connected, Today shows “Connect the apps your squad works in” to the owner. Select Connect an app to open the catalog, or Not now to hide the card.

Connect an app

1

Open the catalog

On Connected apps, click the Add integration card.
2

Find the app

Scroll the categories, or type in Search the catalog. Your connections takes you back to your list.
3

Open the connect window

Click the app. The window Connect followed by the app name opens.
4

Choose the access level

Under What every teammate can do, select the access level for your teammates. The level marked Recommended is already selected. See Choose an access level.
5

Choose who may use it

If your squad has other people in it, the window also shows Share this account with everyone in this squad. It is ticked for the owner and clear for everyone else. Leave it ticked to let your teammates 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. The button shows Opening… while the sign-in starts.
7

Approve access

In the new browser tab, sign in to the app and approve access. The Squad window says “Your browser is open on” and the app’s sign-in, and waits.
8

Return to Squad

Go back to the Squad tab. The window closes by itself when the new account shows up.
On Squad for Mac (private beta), see Connect an app from the Mac. The catalog shows the apps in these categories, in this order: Recommended, Productivity, Communication, Developer tools, CRM, Marketing, Storage, Analytics, Scheduling, E-commerce, and Other.
A teammate can also ask you to connect an app in chat. The chat card shows a Connect button for the app and a Not now button. The button starts the same sign-in, at the app’s recommended level.

Check that it works

  • The app shows under Your connections in its own card, with a row for the account. The row shows the account name and its access level. The count beside Your connections says how many apps are active.
  • In the catalog, the app card shows Connected and Add account.
  • After a teammate uses the account, the row shows “used” and the time, and the app card shows the number of accounts and “last used” with the time.

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 a teammate makes and refuses any action that is outside the level you chose. Squad filed every action of every app by hand in the lowest level that should allow it:
  • Read-only reads everything the account can see and changes nothing.
  • Each level above it says what it adds and what it leaves to the level above. For example, Read + send in Gmail and Outlook writes, replies to, forwards, and sends mail, but it does not label, move, archive, or delete mail. Read + send in Slack posts, edits, and deletes your messages, but it does not manage channels.
  • Sharing, members, settings, credentials, webhooks, and permanent deletes sit at the top level of each app.
  • In Stripe, Supabase, BigQuery, Gong, and Canva, the top level is Read + write. Their administration and credential actions run at no level, so no teammate can run them.
Other points:
  • 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. The window marks it Recommended.
  • Under each level, the window says what it allows and what it does not.
  • An account that you connected before access levels existed holds the app’s top level, and its row shows that level.
  • An account whose saved level the app no longer offers shows “No access until you choose a level”. Its teammates can run no action in it. Open Manage scope and pick a level.
Each app has a manual that lists what your teammates can do at each level, for example the Gmail manual. The connect window links to it with See everything your teammates can do in followed by the app name and at each level. To change the level of a connected account:
  1. Under Your connections, click the level on the account row. You can also click the ⋯ menu on the row and click Manage scope.
  2. Under What every teammate can do, select a different level.
  3. Click Save access.
You do not sign in again. The change applies from each teammate’s next call. A Collaborator can change the level only of accounts that they connected. Routines and triggers use the same accounts and the same levels. A routine that, for example, labeled Gmail messages at Read + send is now refused. Raise the account to Full access if the routine needs it.

Limit a single teammate

By default, every teammate uses the level of the account. You can narrow the level for one teammate, or block one teammate from the account. Only the owner and Administrators can do this.
1

Open the account scope

Under Your connections, click the level on the account row.
2

Find the teammate

Under One teammate at a time, find the teammate.
3

Choose the teammate's level

In the teammate’s list, select one option:
  • Default (the account’s level, shown in parentheses)
  • any level of the app
  • No access
4

Save

Click Save access.
The change applies from the teammate’s next call. Squad checks the account level first, so a teammate setting cannot give a teammate more than the account level. A teammate with No access does not see the account in its list of connections.

Connect more than one account

You can connect several accounts of the same app, for example two Gmail inboxes.
  1. Under Your connections, click + Account on the app’s card. You can also click the app in the catalog, where it shows Add account.
  2. Choose the access level for the new account. If your squad has other people in it, also choose whether to tick Share this account with everyone in this squad.
  3. Click Connect followed by the app name, and sign in with the other account.
Each account is a row in the app’s card. The row shows the account name and its level, followed by Main account on the main account and Shared on an account that everyone may use. Two accounts with the same name get a number after the name until you rename one. Each row has a ⋯ menu (Actions for this connection) with these actions: Disconnect… opens a dialog, “Disconnect” and the account name, that says “Your teammates lose access to” the app “through this account.” Click Disconnect to remove it. To use the account again, you connect it again. While an action runs, the row shows Working…. If it fails, the message shows at the top of the page. When an account’s sign-in expired, its row shows Needs reconnecting, and the person who connected it also gets a Reconnect button. The app counts as active again once one of its accounts works. You can also ask a teammate to do these actions for you, except Reconnect: rename an account, change its access level or one teammate’s access, share it or stop sharing it, make it the main account, or disconnect it. The same rules apply as on this page. Ask in your own conversation with the teammate, because a connected account belongs to one person. See Connected apps.

Who can use an account

Each connected account belongs to the person who connected it: you, or another person in your squad. That person decides who else may use it. This matters only when other people are in your squad. See Invite people to your squad. An account is private or shared:
  • Private: only the person who connected the account can use it through your teammates. The row shows no tag. An account is private unless the person who connected it ticked the share box when connecting. The accounts that you connected before other people joined stay private until you share them, for example with the share box when you invite someone. See Share your accounts when you invite.
  • Shared: everyone in the squad can use the account through your teammates. The row shows Shared after the level.
To change it, click ⋯ on the account row, then click Share with teammates or Stop sharing with teammates. Only the person who connected the account can change it. You and your Administrators cannot share another person’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 teammate keep Disconnect…, Make it the main account, Rename, and Manage scope on every account. When you connect a new account in a squad that has other people, the window shows the box Share this account with everyone in this squad. The box is ticked for the owner and clear for everyone else. When it is ticked, the window says “Your teammates can use it for anyone’s requests. You can stop sharing it later from its menu on this page.” When it is clear, it says “Only your own requests can use it. You can share it later from its menu on this page.” 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 “Teammates 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.” “Integrations” there means the Apps page. A card for a connection that expired shows no box. Its button Reconnect in Integrations opens the Apps page. On Squad for Mac (private beta), the connect card asks the same question, with the box Share this account with everyone in this squad and the same default. When the box is ticked, the card says “Your teammates can use it for anyone’s requests. You can stop sharing it later in Settings, under Apps.” When it is clear, it says “Only your own requests can use it. You can share it later in Settings, under Apps.” A card that reconnects an account shows no box. A squad has other people once someone accepted an invite. An open invite does not count. For the owner and Administrators, an account that another person connected shows “connected by” and that person’s name on its row. An account that the owner connected shows no name. How teammates pick an account:
  • A teammate works for the people whose messages it is answering, or for the person who started or reassigned a task. Heartbeats, email, and messages from Telegram, Discord, or Slack count as work for you. A routine uses the accounts that its Accounts it can use setting allows. See Choose the accounts of a routine.
  • It uses only an account that each of those people may use. In a chat where you and another person both write, the teammate can use your private account when it answers you, and not when it answers the other person.
  • When a teammate does not pick an account, it uses the people’s own account first, then a shared account. Within each group, the account marked Main account comes first.
  • When no account of the app may be used, the teammate tells you who connected the account and what fixes it. They can connect their own account on the Apps page, or the account’s owner can share it.
What other people in your squad see:
  • A Collaborator, or an Administrator limited to some teammates, sees only their own accounts in Your connections. They connect their own accounts in the same way as you.
  • For a Collaborator or a Viewer, accounts that other people shared show at the top of the page in a separate card, Shared with you: “Accounts other people in your squad let everyone use. Your teammates can act with them too.” Each shows “Shared by” and the person’s name. They cannot change these accounts. An Administrator limited to some teammates does not see this card. On Squad for Mac (private beta), such an Administrator sees it too.
  • Only you and the Administrators who can see every teammate see every account in the squad.
  • Only you and your Administrators see Custom integrations and the Recommended apps in the catalog.
  • A Viewer cannot connect apps and has no + Account, Reconnect, or ⋯ menu. The level on each row is plain text. With no accounts of their own, the page says “Your access is view-only, so you can’t connect apps here. Anything shared with the squad is listed above.”
Only the person who connected an account can use Reconnect on it. When a person leaves the squad or you remove them, the accounts that they connected are disconnected, and app event triggers on those accounts pause. The Recommended category is first in the catalog. Only the owner and Administrators see it. 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: teammates never get the tool that buys credit packs. Squad removes it.
  • PostSyncer: teammates 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.
For Bazzly, create the API key with the read and write scopes only and leave top-ups off. The key is the only spending control.
After you connect a Recommended app, its tools reach your teammates within a couple of minutes. The app shows Connected in the catalog and appears in the list under Custom integrations, not under Your connections. To replace the key or disconnect, click the app in the catalog. For SiteGPT, Sign in again to replace the credential replaces the sign-in. For the other apps, click Replace the stored key. To disconnect, click Disconnect, then Really disconnect? to confirm. Revid and PostSyncer show in the catalog only when your squad’s computer runs a recent enough version of the Squad software. If they are not in the catalog, your squad’s computer is still updating.

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 and usage > Billing. See Manage your subscription, credits, and workspace data. A teammate says an action is not allowed on the account. Cause: the action is outside the account level or the teammate’s level. Fix: raise the level with Manage scope, or change the teammate’s line under One teammate at a time. To see which level an action needs, open the app’s manual, or ask the teammate. It can see which levels run each action. A routine that worked before is now refused in an app. Cause: the access levels were reviewed, and some middle levels hold less than before. For example, Gmail Read + send no longer labels or archives mail. Fix: raise the account’s level with Manage scope. A teammate says that no account of an app can be used for another person. Cause: the app accounts in the squad 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 teammates. See Who can use an account. A routine says that no account of an app can be used. Cause: the routine 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 routine with Shared accounts and my own accounts. See Choose the accounts of a routine. A teammate says the connection expired. Cause: the app ended the sign-in. The account row shows Needs reconnecting. Fix: click Reconnect on the row, or click ⋯ and Reconnect. Then click Reauthorize on and the app name, and sign in again. For the owner and Administrators, a connection that needs you also shows on Today under Needs you, with “Reconnect” and the app name. 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. The page shows “No connections yet”. Cause: no app is connected yet. Recommended apps do not show under Your connections. They show under Custom integrations. Fix: click Add integration and connect an app.

Other messages

For Recommended apps, the app’s window can show: When a teammate 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].” The level is the level that the account holds now. Raise it with Manage scope.
  • “Your agent policy restricts you to “[level]” access on this account, which does not include [action].” Here the level is the level’s short internal name, for example read_write. Change that teammate’s line under One teammate at a time.
  • “You do not have access to this connection. Ask the workspace admin to update your access in the Integrations page.” The teammate has No access under One teammate at a time.