Skip to main content
You can bring the people you work with into your squad. A person signs in to the dashboard with their own email address, sees your squad’s work, and, except a Viewer, talks to your teammates. Billing always stays with you. Each person you invite uses a seat. The owner does not. You buy seats in Billing, then you invite people into them on People. When every seat is taken, your invite on People can add the seat for you. For the other ways to show your work to people, see Share a read-only view of your workspace and Talk to your squad from Telegram, Discord, or Slack.

Before you start

  • You must be the owner to buy seats. An Administrator who can see every teammate can invite people into seats that you already bought.
  • Decide which role each person gets. See Choose a role.
  • Know what the person will see. People can read the full chat history of every teammate that they can see, including your messages. See What people share with you.
A seat is a paid add-on. Each seat is a monthly charge on your subscription. The app shows the price before you buy. See What Squad costs.

Open People

Select Settings at the bottom of the sidebar, then People. The People page opens. The page has up to two cards:

Buy seats

1

Open Billing

Select Settings, then Billing and usage.
2

Set the number of seats

On the seats card (Seats for people: and the numbers), use − and + to set how many seats to buy. You can buy 1 to 100 seats at a time.
3

Select Buy

Select Buy followed by the number of seats and the monthly price.
4

Confirm

Read the dialog. It says that your card on file is charged now for the rest of the billing period, pro-rated, that each renewal after that includes the new seats, and how many seats you go to. Select the buy button in the dialog.
While Squad updates your subscription, the card says Updating your seats…. The card then shows the new number of seats. See Manage your plan and billing. An invite into a free seat never charges your card. When every seat is taken, your own invite can buy one seat for that invite. See Invite when every seat is taken.

Choose a role

Invite someone offers three roles in Role. The line under the fields says what the chosen role does. Collaborator is selected when the page opens. You can change a person’s role later. See Change a person’s role.

Invite someone

1

Type the email address

In Email, type the address that the person will sign in with.
2

Choose the role

In Role, pick Collaborator, Administrator, or Viewer.
3

Select Send invite

Select Send invite, or press Enter in Email. A sheet opens, for example “Invite name@example.com as a Collaborator?”.
4

Read the sheet and send

The sheet says what the person will see and do. Select Send invite. To stop, select Cancel.
The sheet tells you:
  • The person gets an email link that works for 7 days.
  • Accepting joins them to this squad as the role that you chose, and holds one of your seats until you remove them or revoke the invite. It names the seat price.
  • What the role can do, in the words of the table below.
  • “They start with every teammate in this squad. After they join, you can limit them to some teammates here.”
For a Collaborator or an Administrator, the sheet also has one line about your connected apps. When it shows the share box (see the next section), the box replaces this line. Otherwise the line is:
  • For a Collaborator: “The apps you connected stay private to you. They connect their own in Settings → Apps, and you choose there which of yours to share with the whole squad.”
  • For an Administrator: “The apps you connected stay private to you. They connect their own in Settings → Apps. They can disconnect any account there, but only the person who connected an account can share it.”

Share your accounts when you invite

When you invite a Collaborator or an Administrator and some of your connected app accounts are still private, the sheet also shows Share my connected accounts with everyone in this squad, with the names of up to four of those accounts and how many more there are. The box is ticked each time the sheet opens.
  • Leave it ticked to share these accounts when the invite is sent. Your teammates can then use them for anyone’s requests. You can stop sharing any of them later in Settings > Apps.
  • Clear it to keep your accounts private. Each person then connects their own accounts in Settings > Apps.
Only the owner sees this box, and it shares only the owner’s accounts. It does not show for a Viewer invite. After you send, the card says “Invite sent. The link works for 7 days.” If the invite shared accounts, it adds, for example, “Your 2 connected accounts are now shared with everyone in this squad.” The invite shows in People in your squad with Invited · and its role, how long ago it was sent, and the days until the link expires. An open invite uses a seat. Next to Send invite, the card shows how many seats are free, for example 2 of 3 seats free. While a seat purchase or release is still being applied, Send invite does not work. When no seat is free:
  • An Administrator sees no form. The card says, for example, “All 3 seats are in use. Ask the squad owner to add another seat.” With no seats at all, it says “There are no team seats yet. Ask the squad owner to add seats before inviting people.”
  • You keep the form, and the button adds a seat. See Invite when every seat is taken.
To send a new link to the same person, invite the same address again. The new link replaces the old one, which stops working, and uses the same seat. This works for you also when every seat is taken, and it buys no seat.

Invite when every seat is taken

When every seat is taken, or your squad has no seats yet, the owner’s invite adds a seat. An Administrator cannot add seats.
1

Type the address and choose the role

In Email, type the address. In Role, pick the role. The button reads Invite and add a seat with the monthly price of a seat.
2

Open the sheet

Select Invite and add a seat. The sheet says “Every seat is taken, so this adds one”, with the monthly price, and that your card is charged now for the rest of this billing period. It also says that the invite goes out once the seat is ready.
3

Add the seat and invite

Select Add a seat and invite. To stop, select Cancel.
Check that it works: until the seat is added, the invite shows in People in your squad with Invite · and its role, and “Adding a seat. The invite goes out as soon as it’s added.” Then the invite goes out on its own, also if you leave the page, and the row shows Invited · and its role. On Squad for Mac, adding a seat and inviting works the same way, and the invite also goes out if you leave People. While it waits, its row shows the address, its role, and “Adding a seat. The invite goes out as soon as it’s added.” If the request fails at once, the card says “The seat couldn’t be added, so the invite hasn’t gone out.”
  • Squad buys exactly one seat, and only when the invite needs one. If you confirm the same address again while it waits, no second seat is bought. If a seat frees up before you confirm, the invite goes out at once and nothing is bought.
  • If you left the share box ticked, the invite shares only the accounts that the sheet listed.
  • A seat that was bought for a waiting invite cannot be released.
  • If the seat cannot be added, the invite does not go out. A line in Activity says which invite did not go out and why. If the request fails at once, the card says “The seat couldn’t be added, so the invite hasn’t gone out. Try again.”
  • A squad reset drops the invites that wait for a seat.

What the invited person does

1

Open the email

The email has the subject “[Squad]” followed by “(your name) added you to their squad”. It says that there is no plan to buy and no card to enter.
2

Open the invite

Select Accept invite in the email. The invite page names you, the role, and the email address that the invite is for.
3

Sign in

Select Sign in to accept. Sign in with the invited email address. A person with no Squad account selects Sign up on the same page and creates one with that address.
4

Accept

Select Accept invite. The dashboard opens on the squad. In Switch squad, it says Shared with you.
The link works once, and only for the invited address. A person you invite does not need a subscription of their own.

Limit a person to some teammates

A new person can see every teammate. You can narrow that list.
1

Open the list

In People in your squad, select All teammates on the person’s row. The button shows, for example, 2 of 5 teammates when the list is already narrowed. Your own row has no such button.
2

Choose the teammates

In the sheet Which teammates can and the name talk to?, clear Every teammate, including ones added later. Then check the teammates that this person may use.
3

Save

Select Save access. To stop, select Cancel.
A teammate that you leave out disappears for this person: its chat, its tasks, its questions, and its activity. Group chats stay shared. With Every teammate, including ones added later checked, the person also gets teammates that your chief of staff hires later. You can also check no teammate. The sheet then says that the person sees no teammate, only group chats, and the person stays in the squad. If the save fails, the sheet says “That access couldn’t be saved. Try again.” An Administrator whose list is narrowed cannot make changes that reach every teammate. They cannot:
  • Invite people, change roles, or change another person’s teammates.
  • Hire teammates, or change AI accounts, the squad’s AI, tools, or skills. The dashboard does not offer them these controls, for example the + beside Your squad. Your squad’s AI and More on Settings > AI are read-only for them. A skill’s switch says “Only the squad owner or an Administrator who works with every teammate can turn skills on or off.” They can still choose which skills one of their own teammates uses, on its Setup.
  • Add, change, or remove custom integrations: API keys, MCP servers, and their sign-ins. They do not see Custom integrations on Apps.
  • Add an extra Telegram bot, a Discord bot, or a Slack bot that is not tied to one teammate, or set a bot’s Answered by to Your chief of staff.
  • Search, edit, forget, or clear the squad’s memories, or change its memory switches. In the dashboard, the Memory screen still shows the files of their teammates and the memory switches, which they cannot change. In place of the squad’s memories, it says Your squad’s memory isn’t shared with you. See Memory.
  • See or move the triggers of a teammate that was removed.
  • Manage connected accounts other than their own, or make any account the main account. On the Apps page, they see only their own accounts, and the accounts that other people shared in Shared with you.
To give an Administrator these powers, check Every teammate, including ones added later for them.

Change a person’s role

In People in your squad, open the role menu on the person’s row (the name and ’s role) and pick Collaborator, Administrator, or Viewer. The row shows Saving… until Squad saves the change, then the new role. If Squad refuses the change, the card says “Couldn’t change their role.” and the old role stays. Nobody can change their own role or their own teammate list. Only you and the Administrators who can see every teammate can change other people.

See what a person did

Select Activity on a person’s row. The panel shows Last seen and how long ago, or They have not opened Squad yet., then Questions they answered, their Task comments, and their messages in Squad chat. Each item shows how long ago it happened. For how many items each section shows, see Limits and defaults. Squad reads the activity again each time you open the panel. If it cannot load, the panel says “Activity couldn’t load:” and the reason. Select Hide activity to close it. A Collaborator or a Viewer can open the panel on their own row only.

Remove a person or revoke an invite

  • To take back an invite that nobody accepted yet, select Revoke on the invite’s row. If it fails, the card says “Couldn’t revoke the invite.”
  • To remove a person, select Remove on their row. The dialog “Remove” followed by the name says that they lose access right away, that every account they connected is disconnected, and that bringing them back takes a new invite. It also says that their seat stays on the subscription for the next person you invite until it is released. Select Remove. If Squad refuses, the card says the name and “couldn’t be removed. Try again.”
A removed person loses access at once. The app accounts that they connected are disconnected. The tasks, docs, and comments that they wrote stay in your squad. You can also ask a teammate to invite someone, revoke an invite, change a person’s role or teammate list, or remove a person. Ask in your own conversation with the teammate, not in a group chat. The same roles apply as on this page, and nobody can change their own role or teammate list this way. When every seat is in use, the invite fails until the owner adds a seat. See People. Removing a person or revoking an invite frees the seat, but you keep paying for it. The same is true when a person leaves or you reset the squad. You can invite someone else into it, or release it.

Release unused seats

1

Open Billing

Select Settings, then Billing and usage.
2

Select Release

On the seats card, select Release followed by the number of unused seats and the monthly saving. The button shows only when at least one seat is free.
3

Confirm

Read the dialog, for example “Release 2 unused seats?”. It says how much your subscription goes down each month. Select Release followed by the number of seats.
You cannot release a seat that a person or an open invite uses, or a seat bought for an invite that is still waiting to go out. Squad refuses with “Those seats are in use. Remove people or revoke invites first.”

What people share with you

  • Chat history. Chats with teammates are shared squad history, not private messages. A person reads every conversation of each teammate that they can see, including yours. Unread replies and reply notifications in the bell count for each person only in the conversations that they are in: they wrote in them or forked them. See Which replies are new for you.
  • Your cloud computer. Each teammate has its own browser, but the computer is shared by the squad. A site that someone signed in to there may be usable by other people in the squad through the teammates. The keys and secrets that you saved for custom integrations work the same way. When other people are in your squad, the computer screen says so above the teammate’s screen. See Watch or take over a teammate’s computer.
  • Memory. Your squad has one memory for everyone. While the memory switches are on, it learns from chats, tasks, routines, and heartbeats, from every person in the squad. It does not learn from work that starts with an email to a teammate’s inbox or with a trigger’s event. It gives teammates what bears on a request, whoever asked. A fact from your chat can come up when a teammate works for another person, and the reverse. Teammates are told not to save a secret there that one person must not see. See How your squad learns and Turn memory on or off.
  • Connected apps are per person. Each app account belongs to the person who connected it, and it is private unless that person shares it. Your own accounts are private too, so other people’s requests cannot use them until you share them. Nobody else can share them. See Who can use an account.
  • Projects and contacts. Projects and contacts are shared squad work. Owners, Administrators, and Collaborators can change them, and a Viewer can read them.

How teammates treat people

  • A teammate knows who wrote each message in the dashboard chat. It answers a person by name and reports the result back to that person.
  • A teammate uses only the app accounts that the people it works for at that moment may use. If a person asks for an app that only you connected, the teammate says whose account exists and what fixes it: the person connects their own account, or you share yours.
  • A teammate does not repeat what it got with your account to a person who may not use that account.
  • Before a person signs in to a site on your cloud computer, or gives a teammate a password, the teammate tells them that other people in the squad may be able to use that sign-in. For an account that they want to keep to themselves, it points them to the Apps page.
  • A teammate asks for a password or personal details in a form card, never in chat. Only the owner can answer a form card. When the work needs another person’s own password or details, the teammate does not ask the owner to type them. It tells that person which site and fields the step needs, and pauses that work until the person connects their own account in Settings > Apps, or the owner saves a shared sign-in in Custom integrations.
These are instructions that teammates follow. Squad itself enforces the app account rules when a teammate uses an app.

Teammates work within the person’s role

A teammate does for a person only what that person can do in the dashboard, with the exceptions in What the limits do not cover. Squad checks the Squad actions that a teammate takes, such as a task change, an email send, or a change to a teammate, against the role and the teammate list of the person that the teammate works for.
  • People limited to some teammates. The teammate cannot use, read, or change the work of teammates that are not on the list. It also cannot make changes that reach every teammate, such as hiring a teammate or archiving every open question. When the teammate @mentions a teammate that is not on the list in a task comment or a question, that teammate is not notified. Squad refuses a post in Squad chat that names such a teammate. The teammate also cannot send a direct message to such a teammate or read its direct messages.
  • Credit balance. Research results, research price estimates, and app actions that a teammate gets for another person do not include your credit balance. This is also true for an Administrator. The credits that each call costs still show, and an estimate still says whether the work fits.
  • Several people at once. When one reply serves several people, for example in a group chat, the teammate can do only what every one of them can do.
  • Helpers. A helper that a teammate starts keeps the limits of the person that the work is for. If Squad cannot tell whom a helper works for, it can do only what a Collaborator can do. This applies only after another person has joined.
  • Your own requests. Work for you is not limited, unless Squad cannot trace it to you (see Helpers). This includes your dashboard chat, Telegram, Discord, Slack, the teammates’ own routine checks, and routines that run in a teammate’s main session.
When Squad refuses an action because of an Administrator’s or a Collaborator’s role, Squad tells the teammate to ask whoever can say yes itself, in a question, and to tell the person that it did. That is you, or you or an Administrator when an Administrator’s role allows the action. For an action that stays with you, such as adding or deleting an inbox, it is you. When the person asked answers yes, the teammate works for them, so it can then do the action. For a Viewer, every action that the role blocks, such as changing a task, saving a contact, or changing a routine, is refused with a sentence that the role is view-only and that you can change it. Asking a question is work that a Viewer’s teammate cannot do, so the teammate asks nobody. For a Viewer, do it yourself or change their role. When one reply also serves a Viewer, for example in a group chat, the teammate asks no question either. It tells the person who asked that you, or you or an Administrator, can do it. Teammates follow what the refusal says: they ask in a question when it says to, and otherwise tell the person what it says. They are told not to retry the action until the person asked says yes, and not to get it done another way, for example through another teammate or a routine. See Answer a question. Teammates also know each person’s role and, for a person limited to some teammates, which teammates they can use.

What the limits do not cover

  • Single memories. While Squad memory is on, a teammate saves, searches, and forgets single memories for anyone it works for, also for a Collaborator or a Viewer who cannot open the memory screen. No teammate can clear all memories, whoever it works for. See Manage what your squad remembers.
  • Your cloud computer. The limits apply to Squad actions, not to what a teammate does on the shared computer, such as its files or its browser. They do not keep sign-ins on the computer apart. See What people share with you.

What stays with the owner

These things are yours alone, whatever role a person has:
  • Billing, credits, seats, and refunds. Other people never see the Billing page or your credit balance.
  • Switching research tools on or off, because they spend credits. An Administrator cannot switch them, on Billing or through a teammate. An Administrator who works with every teammate still switches MCP servers. See Research tools.
  • The saved values of your Secrets: the keys and secret values of your custom integrations. An Administrator who can see every teammate can add, replace, rename, or remove custom integrations, but never sees the saved values. See Add an MCP server or an API key.
  • Resetting the squad.
  • Changing the Telegram user ID that the main Telegram bot answers. See Change your Telegram user ID.
  • Your Mac, with Squad for Mac. Only your own work reaches it. When a teammate works for another person, Squad refuses its Mac requests.
  • Adding an inbox, because an inbox is a charge on your subscription. A teammate can add one only for you, and asks you first when the inbox adds a paid seat. See Your squad’s settings.
  • Questions that ask for access or for an action that only you can do, unless a teammate asked another person. Then that person can answer, and so can an Administrator. A Collaborator or an Administrator can answer decision, approval, and input questions. A Viewer can read them but not answer. See Who can answer.
  • Chat cards that ask to connect an app, add an MCP server, save a key, or fill a form are meant for you. Other people see them without buttons. See Answer chat cards.
A Collaborator or a Viewer also cannot open the computer screen, the memory screen, Public dashboard, Backup, Domains in Settings > Email, or Telegram, Discord, and Slack in Settings > Apps.

Leave a squad

A person that you invited can leave on their own.
1

Open General

Open Settings > Squad > General.
2

Start leaving

In Danger zone, select Leave squad….
3

Confirm

In the dialog “Leave this squad?”, select Leave squad. To keep access, select Stay.
The person loses access right away, and their seat frees up. You keep paying for the seat until you release it. Activity shows that they left. As the owner, you cannot leave your own squad.

Check that it works

  • The invite row shows Invited · and the role you chose until the person accepts. Then the person shows in People in your squad with their role and how long ago they joined.
  • The person’s Settings > Squad > General says “You are a Collaborator in this squad.” (or their role).
  • A message from the person in a teammate’s chat shows their name. The teammate answers them by name.

Troubleshooting

Connect apps: who can use an account

What Squad costs: seats for people

Share a read-only view of your workspace

Settings reference