> ## Documentation Index > Fetch the complete documentation index at: https://squad.so/docs/llms.txt > Use this file to discover all available pages before exploring further. # Invite teammates to your workspace > Buy team seats, invite people by email, choose their role, limit them to some agents, and remove them when they leave. You can bring the people you work with into your workspace. A teammate signs in to the dashboard with their own email address, sees your squad's work, and, except a Viewer, talks to your agents. Billing always stays with you. Each teammate uses a team seat. You buy seats on the **Team access** screen, then you invite people into them. For the other ways to show your work to people, see [Share a read-only view of your workspace](/docs/sharing) and [Talk to your squad from Telegram, Discord, or Slack](/docs/channels). ## Before you start * You must be the owner of the workspace to buy seats. An **Administrator** who can see every agent can invite people into seats that you already bought. * Decide which role each person gets. See [Choose a role](#choose-a-role). * Know what the person will see. Teammates can read the full chat history of every agent that they can see, including your messages. See [What teammates share with you](#what-teammates-share-with-you). A team seat is a paid add-on. Each seat is a monthly charge on your subscription. The **Team access** screen shows the price before you buy. See [What Squad costs](/docs/costs#team-seats). ## Open Team access Open the account menu and click **Settings**. Under **CONNECTIONS**, click **Team** ("Invite human teammates and manage access"). The **Team access** screen opens. The screen has up to three cards: | Card | Who sees it | What it holds | | - | - | - | | **TEAM SEATS** | Only you, the owner | How many seats you have and how many are in use, and the buttons to buy or release seats. | | **INVITE A TEAMMATE** | You, and each **Administrator** who can see every agent | The role choice, the email field, and **Send invite**. The top right corner shows how many seats are free. | | **YOUR TEAM** | Everyone in the workspace | You, marked **Owner**, and each teammate with their role. You and your Administrators also see the open invites. | ## Buy team seats On the **TEAM SEATS** card, type how many seats to buy. You can buy 1 to 100 seats at a time. Click **Buy** followed by the number of seats and the monthly price. Read the dialog. It says that your card on file is charged now for the rest of the billing period, pro-rated, and that each renewal after that includes the new seats. Click the confirm button. While Squad updates your subscription, the card says **Updating your seats…**. The card then shows the new number of seats. An invite never charges your card. Only a seat purchase does. ## Choose a role The **INVITE A TEAMMATE** card offers three roles. | Role | What the dashboard says | What the person can do | | - | - | - | | **Collaborator** | "Works with you: missions, docs, tickets, and chat with the agents you allow." | Chat with agents, work on missions and docs, and answer tickets. Can open Agent Configuration, Skills, Tools, AI Tokens, Runs, Automations (scheduled tasks and triggers), and Email to read them, but cannot change them or stop a run. Connects only their own app accounts. | | **Administrator** | "Runs the workspace with you: team, agents, channels, and settings. Billing stays with the owner." | Everything that you can do, except the things in [What stays with the owner](#what-stays-with-the-owner). Can manage the team, change settings, set up channels, stop runs, and watch or take over an agent's computer. An Administrator limited to some agents can do less: see [Limit a teammate to some agents](#limit-a-teammate-to-some-agents). | | **Viewer** | "Watches the board, missions, docs, and activity. Read-only, no messages." | Reads the same screens as a Collaborator. Cannot send messages, create missions, answer tickets, or connect apps. Can change only their own name and their own notifications, and can leave the workspace. | **Collaborator** is selected when the card opens. You can change a teammate's role later. See [Change a teammate's role](#change-a-teammates-role). ## Invite a teammate On the **INVITE A TEAMMATE** card, click **Collaborator**, **Administrator**, or **Viewer**. In the email field, type the address that the person will sign in with. Click **Send invite**, or press Enter. A confirmation dialog opens, for example "Invite this teammate as a Collaborator?". The dialog says what the person will see and do. Click **Send invite**. The confirmation dialog tells you: * The person gets an email link that works for 7 days. * Accepting joins them as the role you chose, and holds one of your seats until you remove them or revoke the invite. * What the role can do, in the words of the table below. * They start with access to every agent. After they join, you can limit them to some agents. | Role | What the dialog says | | - | - | | **Collaborator** | "They can read the complete chat history of every agent they can see, including your messages and other teammates' messages, and they can send their own." "They can work on missions, docs, and tickets with you. Billing, secrets, and agent configuration stay with you." "The squad computer is shared. By asking an agent, they may be able to use any site signed in on it and the Secrets you saved." | | **Administrator** | The same chat line. "They can run the workspace with you: team, agents, channels, and settings. Billing, refunds, and secrets stay with you." "The squad computer is shared. By asking an agent, they may be able to use any site signed in on it and the Secrets you saved. They can also watch and take over an agent's computer." | | **Viewer** | "They can read the complete chat history of every agent they can see, including your messages and other teammates' messages. They cannot send messages." "Their access is view-only: they can watch the board, missions, docs, and activity, but they cannot change anything." | For a Collaborator or an Administrator, the dialog 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 on the Integrations page, and you choose there which of yours to share with the whole workspace." * For an Administrator: "The apps you connected stay private to you. They connect their own on the Integrations page. 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 dialog also shows **Share my connected accounts with everyone in this workspace**, with the names of those accounts. The box is ticked each time the dialog opens. * Leave it ticked to share these accounts when the invite is sent. Agents can then use them for your teammates' requests. You can stop sharing any of them later on the **Integrations** page. * Clear it to keep your accounts private. Teammates then connect their own accounts on the **Integrations** page. 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 workspace." The invite shows in **YOUR TEAM** with the tag **Invited** and the days until the link expires. An open invite uses a seat. When every seat is in use, the email field is off and the card tells you to buy another seat. An Administrator sees a request to ask you instead: "There are no team seats yet. Ask the workspace owner to add seats before inviting teammates." when you have no seats, or "All N seats are in use. Ask the workspace owner to add another seat." when every seat is in use. 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. When every seat is in use, the email field is off. Revoke the open invite first, then invite the address again. ### What the invited person does 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. Click **Accept invite** in the email. The invite page names you, the role, and the email address that the invite is for. Click **Sign in to accept**. Sign in with the invited email address. A person with no Squad account clicks **Sign up** on the same page and creates one with that address. Click **Accept invite**. The dashboard opens on your workspace. The link works once, and only for the invited address. A teammate does not need a subscription of their own. ## Limit a teammate to some agents A new teammate can see every agent. You can narrow that list. In **YOUR TEAM**, click **All agents** on the teammate's row. The button shows "N of M agents" when the list is already narrowed. Clear **Every agent, including agents added later**. Then check the agents that this person may use. Click **Save access**. An agent that you leave out disappears for this teammate: its chat, its missions, its tickets, and its activity. Group chats stay shared. With **Every agent, including agents added later** checked, the teammate also gets agents that the lead creates later. An **Administrator** whose list is narrowed cannot make changes that reach every agent. They cannot: * Invite people, change roles, or change another teammate's agents. * Add agents, or change AI accounts, agent tools, or skills. * Add, change, or remove custom integrations: API keys, MCP servers, and their sign-ins. * Add a Telegram or Discord bot, or a Slack bot that is not tied to one agent. * Search, edit, forget, or clear the squad's memories on the **Memory** screen, or change its memory switches. They see the switches with the note "You can see these settings, but your role cannot change them." * See or move the triggers of an agent that was removed. * Manage connected accounts other than their own, or make any account primary. Like other teammates, they see other people's accounts only when those accounts are shared, in **SHARED WITH YOUR SQUAD**. To give an Administrator these powers, check **Every agent, including agents added later** for them. ## Change a teammate's role In **YOUR TEAM**, click the role tag on the teammate's row. Each click moves the teammate to the next role, in the order **Collaborator**, **Administrator**, **Viewer**. Point at the tag to see which role the next click gives. Nobody can change their own role or their own agent list. Only you and the Administrators who can see every agent can change other people. ## See what a teammate did Click **Activity** on a teammate's row. The panel shows when they last opened the dashboard, the tickets they resolved, their mission comments, and their messages in **Squad chat**. Click **Hide activity** to close it. A Collaborator or a Viewer can open the **Activity** panel on their own row only. ## Remove a teammate or revoke an invite * To take back an invite that nobody accepted yet, click **Revoke** on the invite's row. * To remove a teammate, click **Remove** on their row. The dialog "Remove NAME from this workspace?" 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 until it is released. Click **Remove teammate**. A removed teammate loses access at once. The app accounts that they connected are disconnected. The missions, docs, and comments that they wrote stay in your workspace. Removing a teammate or revoking an invite frees the seat, but you keep paying for it. The same is true when a teammate leaves or you reset the workspace. You can invite someone else into it, or release it. ### Release unused seats On the **TEAM SEATS** card, click **Release** followed by the number of unused seats and the monthly saving. The button shows only when at least one seat is free. Read the dialog. It says how much your subscription goes down each month. Click **Release** followed by the number of seats. You cannot release a seat that a teammate or an open invite uses. Squad refuses with "Those seats are in use. Remove teammates or revoke invites first." ## What teammates share with you * **Chat history.** Agent chats are shared workspace history, not private messages. A teammate reads every conversation of each agent that they can see, including yours. * **The workspace computer.** Each agent 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 on the squad through the agents. The keys and secrets that you saved for custom integrations work the same way. When your squad has teammates, the computer screen says so above the agent's screen. See [Watch or take over an agent's computer](/docs/computer). * **Memory.** Your squad has one memory for everyone. While the memory switches are on, it learns from chats, missions, scheduled tasks, and heartbeats, from every person in the workspace. It does not learn from work that starts with an email to an agent's inbox or with a trigger's event. It gives agents what bears on a request, whoever asked. A fact from your chat can come up when an agent works for a teammate, and the reverse. Agents are told not to save a secret there that one teammate must not see. See [How your squad learns](/docs/memory#how-your-squad-learns) and [Turn memory on or off](/docs/memory#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 your teammates' requests cannot use them until you share them. Nobody else can share them. See [Who can use an account](/docs/integrations#who-can-use-an-account). ## How agents treat teammates * An agent knows who wrote each message in the dashboard chat. It answers a teammate by name and reports the result back to that person. * An agent uses only the app accounts that the people it works for at that moment may use. If a teammate asks for an app that only you connected, the agent says whose account exists and what fixes it: the teammate connects their own account, or you share yours. * An agent does not repeat what it got with your account to a teammate who may not use that account. * Before a teammate signs in to a site on the workspace computer, or gives an agent a password, the agent tells them that other people on 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 **Integrations** page. These are instructions that agents follow. Squad itself enforces the app account rules when an agent uses an app. ### Agents work within the teammate's role An agent does for a teammate only what that teammate can do in the dashboard, with the exceptions in [What the limits do not cover](#what-the-limits-do-not-cover). Squad checks the Squad actions that an agent takes, such as a mission change, an email send, or a change to an agent, against the role and the agent list of the person that the agent works for. | The agent works for | The agent can | The agent cannot | | - | - | - | | A **Viewer** | Read the squad's work. | Change anything. | | A **Collaborator** | Work on missions, docs, comments, and tickets, post in chat, run research, draft email for your review, and use the app accounts that the person may use. | Add, change, pause, resume, or remove agents. Change skills or skill packs. Add MCP tools. Send email or change email settings. Read your credit balance, estimate credits, or set credit limits. Archive every open ticket. | | An **Administrator** | Everything that you can do, except billing. | Read your credit balance, estimate credits, or set credit limits. | * **Teammates limited to some agents.** The agent cannot use, read, or change the work of agents that are not on the list. It also cannot make changes that reach every agent, such as adding an agent or archiving every open ticket. When the agent @mentions an agent that is not on the list in a mission comment or a ticket, that agent is not notified. Squad refuses a post in **Squad chat** that names such an agent. * **Credit balance.** Research results and app actions that an agent gets for a teammate do not include your credit balance. This is also true for an Administrator. The credits that each call costs still show. * **Several people at once.** When one reply serves several people, for example in a group chat, the agent can do only what every one of them can do. * **Subagents.** A helper agent that an agent starts keeps the limits of the person that the work is for. If Squad cannot tell whom a helper agent works for, it can do only what a Collaborator can do. This applies only after a teammate has joined. * **Your own requests.** Work for you is not limited, unless Squad cannot trace it to you (see **Subagents**). This includes your dashboard chat, Telegram, Discord, Slack, the agents' own routine checks, and scheduled tasks that run in an agent's main session. When Squad refuses an action, the agent tells the person what Squad said, including who can do it instead. Agents are told not to retry the action and not to get it done another way, for example through another agent or a scheduled task. The agents also know each teammate's role and, for a teammate limited to some agents, which agents they can use. #### What the limits do not cover * **Single memories.** While **Squad memory** is on, an agent saves, searches, and forgets single memories for anyone it works for, also for a Collaborator or a Viewer who cannot open **Memory**. No agent can clear all memories, whoever it works for. See [Manage what your squad remembers](/docs/memory). * **The workspace computer.** The limits apply to Squad actions, not to what an agent does on the shared computer, such as its files or its browser. They do not keep sign-ins on the computer apart. See [What teammates share with you](#what-teammates-share-with-you). ## What stays with the owner These things are yours alone, whatever role a teammate has: * **Billing**, credits, team seats, and refunds. Teammates never see the Billing screen or your credit balance. * The saved values of your Secrets: the keys and secret values of your custom integrations. An Administrator who can see every agent can add, replace, rename, or remove custom integrations, but never sees the saved values. See [Add an MCP server or an API key](/docs/custom-integrations). * Resetting the workspace. * Your Mac, with Squad for Mac (private beta). Only your own work reaches it. When an agent works for a teammate, Squad refuses its Mac requests. * Adding an inbox, because an inbox is a charge on your subscription. * Tickets that ask for access or for an action that only you can do. A teammate sees "Only the workspace owner can complete this step." A Collaborator or an Administrator can answer decision, approval, and input asks. A Viewer can read them but not answer. * Chat cards that ask to connect an app, add an MCP server, or save a key are meant for you. A Collaborator or an Administrator can still use a connect card to connect their own account. An Administrator who can see every agent can also add the MCP server or save the key from the card. A Collaborator or a Viewer also cannot open the computer screen, **Memory**, **Public Dashboard**, **Backup & Export**, **Email Domains**, or the Telegram, Discord, and Slack screens. ## Leave a workspace A teammate can leave on their own. Open **Settings** > **General**. In **DANGER ZONE**, click **Leave workspace**. In the dialog "Leave this workspace?", click **Leave workspace**. The teammate loses access right away, and their seat frees up. You keep paying for the seat until you release it. The Live Feed shows that they left. As the owner, you cannot leave your own workspace. ## Check that it works * The invite row shows **Invited** until the person accepts. Then the person shows in **YOUR TEAM** with their role and the date they joined. * The teammate's **Settings** > **General** says "You are a Collaborator in this workspace." (or their role). * A message from the teammate in an agent's chat shows their name. The agent answers them by name. ## Troubleshooting | What the screen says | Cause | Fix | | - | - | - | | "That does not look like an email address." | The address is not complete. | Type the full address. | | "That is your own email. You are already here." | You typed your own address. | Invite someone else. | | "That person is already a teammate." | The address already belongs to a teammate. | Change their role on their row instead. | | "Every seat is in use. Buy another seat first." | Members and open invites fill every seat. | Buy a seat, revoke an open invite, or remove a teammate. | | "This invite link is not valid" | The link is incomplete or was copied wrong. | Open the link from the invite email again, or ask for a fresh invite. | | "This invite was already handled" | The invite was accepted, revoked, or replaced by a newer invite. | If you accepted it, sign in and open the dashboard. Otherwise, use the newest invite email, or ask the owner for a fresh invite. | | "This invite expired" | The link is more than 7 days old. | Ask the owner to invite the same address again. | | "This invite is for" an address, "but you are signed in as" another | The person signed in with a different address. | Sign out, then sign in with the invited address. | | "This workspace is paused" | The owner's subscription is paused, canceled, or past due. Teammates see this instead of the dashboard. | Only the owner can restore access. After that, the teammate signs in again. | | "You no longer have access to" the owner's squad | The teammate was removed or left. | Ask the owner to invite them again. | | An agent says that it cannot do something for a teammate, for example "A Collaborator cannot send email in the dashboard, so an agent cannot do it for them either." | The teammate's role or agent list does not allow the action. | Do it yourself, ask the person that the message names, or change the teammate's role or agents. See [Agents work within the teammate's role](#agents-work-within-the-teammates-role). | | An agent says "This work is for a scheduled task set to Shared" | The scheduled task uses only the accounts shared with everyone, so it works like a Collaborator. The message says who can change the task: "The workspace owner or an Administrator", or only "The workspace owner" for work that an Administrator cannot do, such as credit limits. | You, or an Administrator when the message names one, save the task with **Shared accounts and my own accounts**. See [Choose the accounts of a scheduled task](/docs/scheduled#choose-the-accounts-of-a-scheduled-task). | | An agent says "This work cannot be traced to one person on the workspace" | Squad could not tell whom the work is for, for example a helper agent whose start was not recorded. Such work can do only what a Collaborator can do. | Ask for it again in your own chat with the agent, or do it yourself. | ## Related This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.