Skip to main content
Connect GitHub so your teammates can work in your GitHub account. You choose an access level for each account, and Squad refuses any teammate action outside that level.

Access levels

Each GitHub account has an access level: Read-only, Read + write code, and Full access. Squad refuses any teammate action outside that level. You can also narrow or block single teammates under One teammate at a time. Read + write code is the recommended level. The connect window selects it for you, and you can choose another level. The GitHub sign-in page asks you to approve full access to your account. This is expected. Squad does not narrow the sign-in. It checks every teammate action against the level you chose, and it refuses actions outside that level.

What teammates can do at each level

Each level opens with a short summary in plain tasks, then lists every action it adds, grouped by what the action works on. You do not need to name actions. Ask in plain words, and the teammate searches for the matching action.
Find an action. Open a level and use your browser’s find (Ctrl+F, or Cmd+F on a Mac) with a word from the task or part of a slug. Or ask a teammate in plain words, for example “What can you do in my GitHub account?” The teammate can search the GitHub actions for you, and it can see which levels run each action.
Each action shows its name, a one-line description where the GitHub action catalog has one, and its slug. The slug is the ID that teammates use when they call the action.
Teammates can use 477 of the 896 GitHub actions at this level:
  • View and search repositories
  • View comments
  • View keys
  • View events
  • View roles and permissions
  • View secrets
  • View and search code
  • View and search commits
  • View and search users
  • View variables
  • View versions
  • View and search labels
All 477 actions at this level:
Teammates can use 896 of the 896 GitHub actions at this level: everything in Read + write code, plus:
  • Create, update, and delete repositories
  • Create, update, delete, and manage secrets
  • Create, update, and delete roles and permissions
  • Create, update, and delete branch protection
  • Update and delete users
  • Create, update, delete, start, and stop codespaces
  • Create, update, and delete variables
  • Create, update, delete, and test webhooks
  • Create, update, and delete tokens
  • Update and delete versions
  • Create, update, delete, and cancel deployments
  • Create, update, and delete gists
The 319 actions that this level adds to Read + write code:

Connect GitHub

Before you start:
  • You need a GitHub account that you can sign in to.
  • Your Squad subscription must be active. Squad does not connect apps while the subscription is not active.
1

Open Apps

Click Settings at the bottom of the sidebar, then Apps.
2

Add an integration

Under Connected apps, click the Add integration card.
3

Find GitHub

Find GitHub in the catalog and click it. You can type the name in Search the catalog.
4

Choose an access level

Under What every teammate can do, choose an access level. It applies to every teammate. The recommended level is marked Recommended.
5

Choose who may use it

If other people are in your squad, 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.
6

Click Connect GitHub

Click Connect GitHub. The GitHub sign-in page opens in a new tab.
7

Sign in to GitHub

Sign in to GitHub and approve the request. The Squad window waits and closes by itself when the account shows up.
Check that it works: GitHub shows under Your connections in its own card, with a row for the account and its access level.

Change the access level

  1. Under Your connections, find the GitHub account.
  2. Click the access level on the account row, or open the account menu (⋯) and click Manage scope. Both open the same window.
  3. Under What every teammate can do, choose the new level.
  4. Click Save access.
The change does not need a new sign-in. Teammates get the new level from their next call.

Set access for one teammate

Every teammate uses the account’s level unless you set something else for it. You can narrow one teammate to a lower level, or block it. Only you and your Administrators see One teammate at a time. The window says “Each teammate can do what’s set above unless you choose otherwise here. A change applies from their next use of it.”
  1. Under Your connections, open the account menu (⋯) on the GitHub account.
  2. Click Manage scope.
  3. Under One teammate at a time, find the teammate.
  4. Choose Default (level name) to follow the account’s level, choose any level of the app, or choose No access.
  5. Click Save access.
A teammate never gets more than the account’s level, even if you choose a higher level for it. Changes apply from the teammate’s next call. A teammate with No access does not see the account.

Use more than one GitHub account

Click + Account on the GitHub card to connect another account. Teammates try the main account first unless they are asked to use a specific one. When other people are in your squad, a person’s own accounts come before shared accounts.
  • After you click + Account, follow the connect steps above.
  • Each account has its own access level.
  • The first account you connect becomes the main account. Its row shows Main account.
  • To change the main account, open the account menu (⋯) and click Make it the main account. Only you and the Administrators who can see every teammate can do this.
  • To tell accounts apart, open the account menu (⋯) and click Rename.
  • Each account is private to the person who connected it unless that person shares it. When other people are in your squad, connecting an account asks whether to share it with everyone. See Who can use an account.

Reconnect or disconnect

Reconnect when the connection has expired, or when you need to change what the account can reach on the GitHub side:
  1. Open the account menu (⋯) and click Reconnect.
  2. Click Reauthorize on GitHub.
  3. Sign in to GitHub and approve the request.
Reconnect signs in to the same account again. It does not add a second connection. Only the person who connected the account can reconnect it. An account whose sign-in has expired shows Needs reconnecting on its row, with a Reconnect button for the person who connected it. Open the account menu (⋯) on the GitHub account and click Disconnect…. A dialog asks you to confirm and says “Your teammates lose access to GitHub through this account.” Click Disconnect. Teammates then lose access to that account at once. If it was the main account, another connected GitHub account becomes the main account.

Costs

GitHub actions do not use Squad credits. Connected apps never use credits. For what does use credits, see What Squad costs.

Troubleshooting

A teammate reports that an action is not allowed on this account.
  • Cause: the action is outside the account’s access level, or outside the level you set for that teammate.
  • Fix: choose a higher level in Manage scope. You or an Administrator can also change the teammate’s row under One teammate at a time.
A teammate says it has no access to GitHub, or it does not see the account.
  • Cause: the teammate is set to No access under One teammate at a time, or the account is not connected.
  • Fix: you or an Administrator opens Manage scope and changes the teammate’s row. If the account is missing, connect it again.
Connecting or saving fails with “Your subscription isn’t active.”
  • Cause: your Squad subscription is not active.
  • Fix: the owner fixes the subscription on the lock screen: Update card after a failed payment, or Subscribe again after it ended. See Use the lock screen.
A teammate says the GitHub connection has expired.
  • Cause: the sign-in for that account is no longer valid.
  • Fix: click Reconnect on the account row, or open the account menu (⋯) and click Reconnect.

Common questions

Each GitHub account has an access level: Read-only, Read + write code, and Full access. Squad refuses any teammate action outside that level. You can also narrow or block single teammates under One teammate at a time.
Click + Account on the GitHub card to connect another account. Teammates try the main account first unless they are asked to use a specific one. When other people are in your squad, a person’s own accounts come before shared accounts.
Open the account menu (⋯) on the GitHub account and click Disconnect…. A dialog asks you to confirm and says “Your teammates lose access to GitHub through this account.” Click Disconnect. Teammates then lose access to that account at once.

Connect apps

Add an MCP server or an API key

Use this when an action you need is not in this app.