What your teammates can do

The areas at a glance

Tasks

• Create a task with a title, a description, a priority (Urgent, High, Normal, or Low), an owner, and tags.
• Move a task through its stages.
• Break a task into steps, each done by the teammate who does that kind of work. The teammate that splits the work creates the task first, assigned to itself because it sees the task through, then each step under it. A step has no steps of its own, and a task holds a limited number of steps. See Limits and defaults. Teammates are told to make a task with steps only when the work has two or more parts.
• Move a step to another task, or make it its own task again.
• Read a task’s steps, and the task that a step belongs to.
• Close a task with steps when its work is done. Squad does not close it by itself: when the last step is done, Squad tells the task’s teammate to close the task or say what is left.
• Comment on a task and @mention other teammates to bring them in. When the newest notes on a task are a long run of teammates’ notes with no person in between, a teammate’s @mention does not wake the teammates it names. The note posts, and the teammate is told that its mention woke no one. See Limits and defaults.
• Mark a task as ongoing, so that the stall check leaves recurring work alone.
• Archive a finished task, move a task to the Trash, and restore it from the Trash.
• Turn an email into a task.
• Post a live status line on the task while they work. It shows in the task’s progress trail.

• Move a task to Needs you directly. Only a question does that. See Questions.
• Assign a task to you. When they need you, they ask a question on their own task.

Create a high-priority task for the writer: a 1,200-word blog post on how to price a SaaS product. Link the draft doc to the task and put it in review when it's done.

Mark the weekly newsletter task as ongoing. It's recurring work.

Questions

• Ask a question on their own task. A question holds one or more asks. Each ask is one type: Access, Decision, Approval, Action, or Input. The task then waits in Needs you.
• Add asks to the open question of a task. A task has at most one open question. A question holds a limited number of open asks, and each ask has a size limit. See Limits and defaults.
• Ask one person in your squad: by name, by email, or by a first name that only one person has. Only that person is told, and the question waits in their Needs you. Teammates are told to do this in a squad with more than one person, when one person can answer, for example the person who asked for the work. When the name matches nobody, or two people, Squad gives the teammate the names of the people who can answer, and it asks again instead of guessing. See Questions for one person.
• Pass one of their own open asks to another person when a person tells them whose it is, for example “that’s Marco’s call”. Only the new person is told. When someone other than the person asked answers, the teammate learns who answered, and asks that person first next time. See Ask someone else.
• Show a question inside the chat, so that you answer it there.
• Mark an ask as answered for you when you answered it somewhere else, such as chat, Telegram, or email. The teammate must quote your own words. Your words are saved on the question. When a teammate closes an ask with the words of another person in your squad, from that person’s conversation in Squad, the answer counts as that person’s. The task’s teammate then works for the people who answered, with their limits. After each message that you send them in the dashboard or Squad for Mac, they get the list of their own open asks that wait on you, so that they close the one that you answered.
• See who set a question for later, and until when. See Set a question for later.
• Withdraw their own asks when they no longer need you, with a reason posted on the task. When a teammate moves a waiting task back to work, Squad withdraws the open asks that it asked on that task. See What teammates can do with questions.
• Archive every open question at once, but only when you ask for exactly that. This also closes the questions for other people. A question that someone set for later stays open while it still waits on them, and the teammate tells you how many stayed. A task with steps stays on the board while its steps still have questions, and the teammate tells you how many tasks stayed for that reason.

• Answer the stall checks that Squad opens when a task goes quiet. Only you can answer those.

• Answer a question on their own judgment, or on a guess about what you would say.
• Put a password or key into a question. They ask you to save it in the vault instead.
• @mention the person in a question that is for them. The question already tells them.
• Ask, remind, or post a question again before the time that a person set it for later. They carry on with the work that does not need the answer. The question comes back to the person by itself, and anyone else that it waits on can still answer it.

Before you send anything to a customer this week, ask me a question and let me approve it.

Clear all of my questions.

Questions about invoices are for Priya. Ask her, not the whole squad.

Chat and cards

• Reply in your chat, in the conversation you wrote in.
• Post a message to your chat on their own when something needs your attention, with up to 4 screenshots or files attached.
• Name the direct conversation that they are in, and rename it when the topic moves. A name that a person gave stays. The teammate’s name then shows as a suggestion. See Work with conversations.
• Read the name and notes of the project that a conversation is in, with each of your messages there. They can also create and change projects, and move your direct dashboard conversation with them into a project or out of one, unless they work for a Viewer. See Projects and Group conversations into projects.
• Post in another teammate’s conversation. The message shows who sent it.
• Reply with a card instead of plain text:

• Post in the Squad chat, and send direct messages to other teammates. You can read both in the dashboard.
• Keep a live status line current, for example “Reading the Google Sheet”. It shows in the teammate’s working message and on About.
• Log an update, decision, milestone, blocker, or research note to Activity.

• Send cards that record your answer in a group chat. There, they use a question card.
• Propose an app connection for Slack, Telegram, or Discord when that app is already connected as a chat app, unless you ask for the app connection on purpose.

• Give you a link to the place in the dashboard when they tell you where to do something. They use the place names that you see, for example Needs you, Tasks, Routines, and Activity. When they cannot tell which names you see, they name the place both ways, for example “Needs you (My Tickets)”.
• Ask for your yes when they can make a change themselves, instead of sending you through steps. In a conversation, they use a choice card. When a task waits on the change, they ask a question with an approval. After a yes, they make the change and say so. They send you steps only for what they cannot do, such as signing in to an account or paying.

• Ask you to paste a password or key as a chat message. They use an A key to add card, or a form card for a page.
• Post only to say “noted” or “confirmed”. Each post can wake other teammates.

When you finish the audit, send me a screenshot of the report in this chat.

Docs

• Create a doc in markdown, with a type: document, brief, deliverable, note, checklist, protocol, or research. A deliverable doc sends you a Deliverable ready notification.
• Link a doc to a task.
• Read, search, and edit docs, and change a doc’s title or folder.
• Create, rename, and delete folders, and give a folder an emoji. A folder must be empty before it is deleted.
• Move up to 100 docs into a folder in one step.
• Pin a doc to the top of the Docs screen, or unpin it.
• Archive a doc, or delete it permanently.

• Restore an old version of a doc. Docs have no version history. An edit replaces the text.
• Pin a doc to your sidebar. Sidebar pins are yours.

File every competitor doc into a folder called "Competitors" and archive the ones older than three months.

Email

• Send a new email, and reply in a thread. A reply goes to everyone on the thread by default.
• Schedule an email to send later, at least 60 seconds ahead.
• List, read, and search their inbox, and download attachments.
• Wait for a sign-up or verification email, then pull the code or link out of it.
• Mark an email as handled. If nobody opened it, this also clears it from your unread count. An email that you opened is not handled until the teammate deals with it, and the teammate does not tell you an email is already read because someone opened it.
• Write a draft for your review. The draft waits in the Drafts tab until you approve it. They can rewrite or discard their own draft.
• Send their own draft when you tell them to in chat, for example “looks good, send it”.
• Escalate an email to you. It shows in the email’s Needs you tab, and you get a notification.
• List their own open escalations, and withdraw one when it no longer needs you, with a reason that shows in Activity.
• Clear their own escalations older than a number of days, when you ask for it. Your words are saved as the reason.
• Turn an email into a task.
• Add and remove allow and block rules on their own inbox.
• Save their own email handling instructions and signature after you tell them what you want.

• Send past the send caps. See Limits and defaults.
• Change the squad’s shared rules, add an inbox, or add a custom domain, unless the person they work for may do that on Email. See Email settings.
• Withdraw another teammate’s escalation.

From now on, reply to scheduling emails yourself, draft anything about pricing for my review, and escalate refund requests to me.

Block every email from spam-domain.com.

Contacts and pipelines

• Search contacts by name, email, domain, handle, or tag, list a pipeline’s people (one stage, or only the people due a follow-up), and list the people of a project.
• Find contacts with filters that combine, such as a pipeline and stage, tags, an address status, no touch for some days, no name yet, do not contact, or followers on a network. They count the matches exactly in one call, and can split the count by kind, tag, address status, stage, pipeline, company, network, or source.
• Export everyone a filter matches as a spreadsheet, with a download link.
• Read one contact in full, with its standing rules first, and see who changed each fact, when, and where it came from.
• Create or update a person or a company, put them in a pipeline with a stage and a next follow-up, put them in projects, add standing rules such as “Always copy their assistant”, or mark them do not contact.
• Log what happened with someone on any channel: a message, a reply, a comment, a mention, a share, a quote, a like, a follow, a form, a purchase, an intro, an unsubscribe, a call, or a meeting. Squad finds the person by an address, or by their account on the network even after a rename, and adds someone it does not know yet. The same post or message is logged once.
• Log a note, research, a decision with what was turned down, or the brief for a meeting before it happens.
• Import contacts from a spreadsheet or another CRM, with their dated past touches.
• Change everyone a filter matches at once: add or remove tags, archive, mark do not contact, set a pipeline stage and a follow-up, or add or remove projects. The first try only says how many it would change and names the first few. The change then runs in the background, and each change shows in the contact’s history.
• Read the possible duplicates with why, the contacts with no name yet, and the addresses that bounced, that nobody reads, or that unsubscribed.
• Merge two records of the same person or company, undo a recent merge, or mark two records as different people so that Squad stops suggesting them.
• Read, create, or change a pipeline: its stages, its custom fields, the rules for what moves people (for example, a quote moves someone to Shared), where an unsubscribe goes, a goal with dates, the teammate who works it, and a stage that starts a deal from a playbook.
• Open, read, and change a deal: its goal, a short line on where it stands now, who it is with, its people and their roles, its standing rules, and its teammate. Add, move, and end its steps, each with an owner, a day, the step it comes after, and how it was promised.
• Record a decision on a deal with what was turned down, link a document with its dates, close a deal with why or open it again, and keep playbooks.
• Read what is next, by whose move, and what is slipping: your squad’s late steps first, then the other side’s, deals that went quiet, follow-ups due, and renewals coming up.

• Save everyone their work brings in, from any channel, without being asked. They leave out the squad’s own people, automated senders, and anyone a person tells them not to keep.
• Search before they add someone, so that a second meeting updates the contact.
• Read a contact or a deal before they act on it: its standing rules and do not contact first. A rule comes before what they remember.
• Give the source of a fact when there is one, such as the email, the page, or the call.
• Log each touch that they make with another tool, such as a message on a network or mail from a connected mailbox.
• Tell you how many contacts a change reaches before they run it, when you asked for the change and the number is larger than you likely expect.
• End a step done or missed, and close a deal with why. They never delete history.
• Write a deal’s line on where it stands each time the deal moves.

• Email a contact marked do not contact from a Squad inbox, or send, reply, or forward to them through a connected mailbox. Squad refuses the send. A mark on a company covers its people and its domain.
• Send a Gmail reply that leaves its recipient to the thread, or mail with a recipient written in a form that Squad cannot read whole, through a connected mailbox while anyone in your squad is marked do not contact. Squad cannot check who that mail reaches, so it asks for a send with the recipients named. A Gmail or Outlook draft sent as it stands, an Outlook reply, and an Outlook forward, are different: Squad reads who they go to from the mailbox and refuses them only when one of those people is marked, or when it cannot read who they go to or finds no one. See Mark a contact do not contact.
• Change a fact that a person in your squad set on a contact: the name, title, company, domain, website, location, industry, or about text. Squad keeps the person’s value and tells the teammate who set it and when, so that the teammate asks first.
• Clear a do not contact mark that a person in your squad set.
• See or set a deal’s money when it works for a Collaborator or a Viewer, or for the squad as a whole. It sees how sure the money is, such as quoted or signed, but not the amount. Only the owner and Administrators see and set amounts.
• Give a step, a deal, or a playbook’s step to a teammate that the person it works for cannot use.

• Log the email of a Squad inbox. Squad does that by itself.
• Save a password, a card number, or health details on a contact.
• Tell a deal’s amount to anyone in your squad other than the owner and Administrators.
• Reach someone marked do not contact in any other way, such as a message on a network or a call. Squad cannot check a message on a network, so the teammate checks the contact first. They clear the mark only when a person in your squad says that the contact asked to hear from you again.

Import the contacts in this spreadsheet into a new pipeline called "Brand outreach", with the stages Researched, Contacted, Replied, and Signed.

How many people in the recruiting pipeline have had no touch in 30 days, by stage?

What's late on the Rivera onboarding, and whose move is it?

Research

• Pick the cheapest tool that answers the question.
• Estimate what a plan will cost before they start, for anyone they work for except a Viewer. For someone other than the owner, the estimate leaves out your balance.
• Ask for fresh data instead of a cached result.

• Read private pages or pages behind your login with these tools. For that, they use the browser on your cloud computer.
• Run research when the tools are off or your balance is too low.

Find 25 heads of marketing at B2B SaaS companies in London with 11 to 50 employees. Only unlock contact details for the 5 best fits.

Summarize what people on Reddit and Hacker News said about our launch this week.

Your connected apps

• See which apps are connected, and which account is the primary one for each app.
• Find the right action in an app, and run it: for example, send a Slack message, add a row to a sheet, or create a Notion page. A search for actions also says which access levels can run each action, so a teammate can tell you which level an action needs.
• Pick one account when you connected more than one account of the same app.
• Attach a file to an app action, such as an image in a LinkedIn post.
• Give an app a temporary link to a large file, such as a video.
• Propose an app to connect, with a card in chat.
• Rename an account, change its access level, share it, make it the primary account, set a teammate’s access to it, or disconnect it, when you ask. See Connected apps.

• Connect or reconnect an app themselves. You sign in to the app from the card or from the Apps page.
• Act outside the access level of the account, or of their own access to it. You set both on the Apps page, or ask a teammate to change them. Every action of an app sits at one access level, and some actions run at no level. When Squad refuses, the message names the level that the connection has.
• See an account that you blocked for them with No access.
• Send, reply, or forward mail, or send a draft, through a connected mailbox to a contact marked do not contact. See Mark a contact do not contact.
• Get an access token from Facebook, for example a page’s access token. Squad replaces every Meta access token in a Facebook result with “withheld by Squad”, so a teammate never needs one.

Every Friday, read this week's closed deals in HubSpot and post a summary in the #sales Slack channel.

Connect my Notion so you can keep the content calendar there.

MCP servers and custom integrations

• Use the tools of MCP servers that you add, from their first run after you add the server.
• Add an MCP server from a URL or a config that you paste in chat.
• Propose an MCP server with a card, so that you add it with one click.
• Ask for an API key by name with an A key to add card. You type the value into the card.
• Use the keys you save on Settings > Apps > Custom integrations, without showing them in chat.

• Connect a server that needs you to sign in on a web page. You add it on Custom integrations.
• Switch one MCP tool on or off. You switch single tools with Tools on the server’s card in Custom integrations. A teammate can switch only a whole server on or off, and only for the owner or an Administrator who works with every teammate. See Skills, tools, and saved logins.
• See or change the saved value of a key. A teammate can list the names of saved logins and keys, and rename or delete one. See Skills, tools, and saved logins.

• Add a server that you did not give them, or make up a server address.

Add this MCP server for the squad: https://mcp.example.com/mcp

Your cloud computer

• Open a page and read it, with a screenshot, in one step.
• Click buttons and links, type, press keys, and scroll.
• Sign in to your accounts with credentials from your vault or the task brief, and use sign-in codes from their inbox.
• Send you a form card when a page needs values that only you know, such as a sign-in. You fill the values in the card, and the teammate types them into the page. See Fill a form that a teammate sends you.
• Take a screenshot of a whole page, and send it to you in chat.
• Ask you to take over when they hit a CAPTCHA, a passkey prompt, an approval in an authenticator app, a file upload, or something that needs a person on screen. The card in chat shows the live screen with Take over.
• Run commands and work with files on the computer.
• Use desktop apps that they open themselves.

• Have anyone but the owner fill a form card. Other people see a form card without fields or buttons. A teammate sends the Your computer needs you card to the owner. On the computer card, an Administrator’s Take over opens the computer screen. See Watch or take over a teammate’s computer.
• Change the version of the software that runs your teammates on the computer. Squad keeps every cloud computer on one tested version and updates it for you, because another version can stop every teammate on the computer. The command is refused, and a teammate that you ask tells you that Squad keeps it up to date.
• Create, change, pause, run, or delete a routine with a command on the computer. The command is refused, and the teammate does it through Routines instead. See Routines and heartbeats.

• Ask for a password in chat, or put card details in a form card.
• Send a form card or a take-over request to anyone but the owner. For another person’s own sign-in, they tell that person which site and fields it needs.
• Work around a site that blocks automated access.
• Accept all cookies for you. They dismiss banners with the most private choice offered.
• Use accounts that are not yours, or put credentials in docs or chat.
• Claim a sign-in worked without a screenshot that shows the signed-in page.

Log in to our Stripe dashboard and send me a screenshot of this month's revenue.

Open our pricing page on your computer and tell me if anything looks broken on it.

Payments

• Ask you to add a payment card, with a card in chat.
• Start a purchase for you with your own card, or with a card that another person shared with you or with everyone. Work for the whole squad, such as a routine set to Shared, can use only cards shared with everyone.
• Pay in a checkout window in their own browser on your cloud computer. They type a stand-in card, not your card number.
• Start a free trial, or use a coupon or an offer that brings the total to 0. This only saves the card with a store that takes cards through Stripe. The teammate names any later charge that the page shows, so you see it where you approve. See Free trials and checkouts that charge nothing.
• Follow the purchase, and confirm it with the order number from the receipt. A card save often has no order number, so the teammate confirms it with the words that the page shows when it is done, such as “Your trial has started”.
• Cancel a purchase before anything is paid.

• Pay without the card owner’s approval. Each payment waits until the card’s owner approves it on their own device. A payment that nobody approves in time pays nothing. See Limits and defaults.
• Have more than one purchase open at a time.
• Pay for a Viewer.
• See or type your card number.

• Put card details in a form card or in chat. They pay only through the card checkout.

Order 200 business cards from the print shop we used last time, with the same design. Use my card and tell me the total before you pay.

Your Mac

• Ask to list a folder, read a file, write a text file, open a web page, see which page is open in your browser (its title and address, not its text), or see your screen.
• In a conversation that belongs to a project with a folder on your Mac, work with the files in that folder without asking each time. A write in a read-only folder still asks. Replacing a file that exists always asks. See Group conversations into projects.

• Do anything on your Mac without your approval on the Mac. You approve once, or for a folder that you share. Screen access is asked every time.
• Reach hidden files, your Library folder, keychains, or system folders, or anything outside your home folder unless you share that folder.
• Use your Mac for another person’s work. Only the owner’s own work reaches the owner’s Mac.
• Give a project a folder on your Mac. Only you do that, on the Mac.

Files

• Read files that you attach in chat. They get a link to each file. A teammate on a Claude Code account gets a copy of each file on your cloud computer, up to a limit. See Limits and defaults.
• Open the files that a person gives them on a task: the task’s own files, the files on a note, and the files sent with an answer to their question. A note or an answer with files wakes the teammate with a link to each file, and so does a task with files that is assigned to them on its own, not with other tasks. A teammate on a Claude Code account gets a copy of each file on your cloud computer, up to a limit. When a teammate reads a task or its notes later, each file has its link too. A file that a person deleted is no longer on the task for the teammate. See Send files with an answer and Delete a file from a task.
• Read attachments on emails in their inbox.
• Attach up to 4 screenshots or files to a chat message they send you.
• Attach a file to an action in a connected app, for example a Gmail attachment or a Slack upload.
• Keep files on your cloud computer for later work.

• Attach a file to an email they send from their Squad inbox. To send a file by email, connect Gmail or Outlook, and the teammate attaches it there.
• Delete a file from a task. A person does that. See Delete a file from a task.

Here's our Q3 sales export. Find the 10 biggest accounts that shrank and write a doc about them.

Routines and heartbeats

• List the routines on Routines, and read one in full, including where it sends its result.
• Create a routine that runs a teammate on a schedule: every so many minutes, at set times in your time zone (for example every weekday at 9:00), or once at a set time. A routine that runs once removes itself after it runs. This is also how they set a reminder for you.
• Change a routine, pause or resume it, run it now, or delete it.
• Choose who does the work, whether each run’s result is posted to chat, a model for the routine, its time limit, and whether it uses your own accounts or only the shared ones. See Choose the accounts of a routine.
• Create a heartbeat for a teammate. A heartbeat is created switched off, and is never on, not even for one run, until someone turns it on.
• Switch a routine to the own accounts of the person who asks, when the routine cannot use them, for example because it was made before or made another way. Teammates are told to make this change themselves when you ask, and tell you it is done, instead of sending you to Routines. See Choose the accounts of a routine.
• Turn on your chief of staff’s 15-minute check-in, but only when you clearly ask for it.

• Create, change, pause, run, or delete a routine for a Collaborator or a Viewer. Only the owner and Administrators can, as on Routines. Squad refuses. For a Collaborator, Squad tells the teammate to ask the owner or an Administrator in a question, and to tell the Collaborator that it did. A yes from the person asked lets the teammate do it.

• Set up the routine themselves when you ask for something to happen regularly, then tell you what they set up, when it runs, and in which time zone.
• Send a reply, a preview, or a reminder back to the chat where the person asked. See How a channel works. Squad points a routine that names no place it can deliver to at the conversation where it was asked for, or else at the teammate’s own chat in the dashboard. See Where a routine reports.
• Finish a routine’s run that a restart cut off, and send its result where the routine reports. See Other work that a restart cut off.

• Turn on a heartbeat without your clear yes. You can also turn heartbeats on yourself in Routines.
• Edit schedule files on your cloud computer. Every routine goes through Routines, because only that records who asked, so the routine can use that person’s own accounts. Squad’s own command for routines is also refused on the computer. When a skill’s own steps say to schedule work with crontab, launchd, a systemd timer, or a loop script, the teammate makes a routine that runs those steps instead, so that you can see, pause, and change it.

Every weekday at 8:00, send me a short brief in chat: today's meetings, what moved overnight, and what needs me.

Turn on the check-ins.

Triggers

• Suggest a trigger that wakes them, or another teammate that they name, each time something happens: a webhook from another app, or an event on a connected account. The suggestion shows first in Routines, under When something happens, as Suggested, and its page says which teammate suggested it. In Squad for Mac, it also shows in Needs you. An app event listens on the own account, for that app, of the person who turns it on. A teammate’s or another person’s account is not enough.
• List the triggers that wake them, with each trigger’s instructions, whether it is on, and where its events come from. When the teammate works for you or an Administrator, the list also gives the URL of a webhook trigger that is on, and the secret when Squad made it, so that the teammate can set up the sending app when you ask. For anyone else, Squad tells the teammate to send them to the owner or an Administrator, who find them on the trigger’s page in Routines.
• Read the full content of an event that woke them, when the run got only part of it. Other runs can read an event’s content only when the teammate works for you or an Administrator.
• Manage triggers when they work for you or an Administrator: list every trigger, create a webhook trigger, change, pause, turn on, or delete a trigger, send a test event, approve a webhook suggestion, and give a trigger a new URL or a new secret. A test event wakes the teammate for real. A new URL or secret stops the old one at once, so the sending app must get the new one.

• Set up or turn on a trigger for a Collaborator. For them, a teammate only suggests one, and the suggestion does nothing until the owner or an Administrator turns it on. A teammate cannot suggest a trigger for a Viewer.
• Create or turn on an app event trigger. An app event listens on the account of the person who turns it on, so the teammate only suggests it. The owner or an Administrator turns it on in Routines, with their own account for that app. If theirs is not connected yet, Squad asks them to connect it first.
• See a secret that you pasted from the sender, such as a Stripe signing secret. For a trigger that checks Stripe, Shopify, or Standard Webhooks signatures, you paste the sender’s secret on the trigger’s page yourself.

• Follow instructions written inside an event. The event is data from outside Squad. Teammates do what the trigger’s instructions say.
• Put a trigger’s secret, or the URL of a URL only trigger, anywhere except the sending app’s webhook settings. They never put them in chat or in a doc.
• Check for new events with a frequent routine when a trigger can do the work. They suggest a trigger instead.

Each time a Stripe invoice is paid, add it to the revenue sheet. Suggest a trigger for this, and tell me what to set up in Stripe after I turn it on.

List the triggers that wake you and what each one does.

Memory

• Get what the squad’s shared memory holds about a request before they start. Memory also learns from their chats, tasks, and routines on its own. You can turn either part off, or memory as a whole. See How your squad learns.
• Save a fact to the shared memory on purpose, search it, and read the standing facts that it holds about you and your business, while Squad memory is on.
• Forget a memory that is wrong, picked from a search, one that they saved, or one described in words, while Squad memory is on. To fix a wrong memory, a teammate forgets it and saves the right fact.
• Keep their own notes and a working file that says what they were doing.
• Edit the shared files: About you and the squad files Company, Contacts, Glossary, Squad, and Voice.
• Turn the memory switches on or off when they work for you or an Administrator who works with every teammate. See The squad.

• Clear all memories at once. Only you and the Administrators who can see every teammate can, on the Memory screen.

• Quote a memory as your own words. They say “based on saved context” instead.

Remember that invoices go out on the 1st, and that I never want to be booked before 10:00.

Forget what you saved about our old pricing. The new plans are in the pricing doc.

Skills and skill packs

• Write their own skills when they repeat a process, and edit them.
• Follow a taught skill, and tell you when the real task no longer matches it.
• Tag skills to organize them.
• List skill packs, turn a pack on or off, add a pack from a public GitHub repository or a folder in one, including a Claude Code or Cursor plugin, update a pack, and remove a pack that you added.
• Turn a single skill on or off for the whole squad, when they work for you or an Administrator who works with every teammate. See Skills, tools, and saved logins.

• Remove a curated pack. They can only turn it off.
• Turn on a pack whose skill names clash with skills already on the computer.

Turn on the marketing skill pack.

You've done the weekly report three times now. Save the steps as a skill.

Your squad

• Hire a new teammate for the squad. This is your chief of staff’s job, when the owner or an Administrator who can see every teammate asks. See Hire a teammate.
• Change their own name, @handle, role, personality, emoji, or bio. Your chief of staff can change these for any teammate.
• Update your name, @handle, and communication preferences, so that teammates address you correctly. This is your chief of staff’s job. It can also note your time zone on your record. The dashboard has no time zone setting, so tell your chief of staff when yours changes.
• Remove a duplicate or test teammate from the squad. Only your chief of staff can remove another teammate. Another teammate can remove itself. Squad removes a teammate only after its email inbox is closed and its open tasks are handed over or finished. See Remove a teammate.
• Pause or resume a teammate, when the owner or an Administrator asks. Your chief of staff can pause or resume any teammate. Other teammates can pause or resume only themselves. A pause from a teammate has the same effect as Pause on the About page.
• Look up any teammate’s status and details.

• Create a second chief of staff. A squad has one.
• Change, pause, resume, or remove another teammate, or change your details, unless they are your chief of staff. Squad refuses with “Only the chief of staff can change, pause, resume or delete another teammate. Ask the chief of staff to do it.”
• Remove your chief of staff or you.
• Restart one teammate. Squad refuses with “There is no restart for one teammate. To stop what they’re doing, use Stop on their run, or Pause them.”
• Hire, change, pause, resume, or remove teammates for a Collaborator or a Viewer. Squad refuses. For a Collaborator, Squad tells the teammate to ask the owner or an Administrator in a question, and to tell the Collaborator that it did. A yes from the person asked lets the teammate do it. See Teammates work within the person’s role.
• Delete a teammate’s inbox for an Administrator. Only the owner can. Squad tells the teammate to ask the owner in a question. See Remove a teammate.

Hire a teammate for customer support. They should handle the support inbox and draft every reply for my review.

Pause [teammate]. Tell me when they are paused.

Your squad’s settings

• A person limited to some teammates gets changes only for those teammates. Changes that reach every teammate, such as the squad’s default model, the memory switches, skills, tools, people, and saved logins, are refused for them.
• When one reply serves several people, for example in a group chat, the change must be allowed for each of them. People, connected accounts, and sharing belong to one person, so a teammate changes them only in a conversation with that one person. Elsewhere, Squad says to ask in the person’s own chat.
• Your own requests are not limited, and neither are your teammates’ own routine checks, such as heartbeats. A routine that uses only the shared accounts has a Collaborator’s access, so it cannot change settings that a Collaborator cannot change. See Teammates work within the person’s role.

What teammates can change, and for whom

What stays with you

• Connecting or reconnecting an app. A teammate can send you a card to connect one. See Connect apps.
• Adding a Telegram, Discord, or Slack bot, which needs its token.
• Connecting, replacing, or disconnecting an AI account. See Choose models and manage AI accounts.
• Saving or changing the value of a saved login or key. See Add an MCP server or an API key.
• Pasting a sender’s signing secret on a trigger that checks Stripe, Shopify, or Standard Webhooks signatures.
• Payments: credits, seats, more squads, billing, refunds, and cancelling. When every seat is in use, an invite fails, and the owner adds a seat on Settings > Billing and usage first. See What Squad costs.
• Your own screen: signing out, switching squads, pins, what you read, and your notification settings.
• Writing in a conversation as you. A teammate brings a teammate into a conversation with an @mention or a message.

When a change takes effect

• “Saved. It takes effect from the next reply.”
• “Saved. Your squad is still applying it, so it takes effect within a minute.”
• “Saved. It takes effect once no teammate is working, usually within a few minutes.” A bot change adds that the previous settings apply until then. Some changes load on your cloud computer only when it restarts, for example a change to who may message a bot. Squad then waits until no teammate is working, so the run that asked can finish its reply. Until then, the earlier settings apply.
• A routine change never restarts anything.

• “The cloud computer is moving to a new machine, so changes to it wait a few minutes. Try again shortly.”
• “Another settings change is still saving on your cloud computer. Try again in a minute.” Nothing was changed. See Limits and defaults.

• Change only what the person asked for, on that person’s word, then say what changed.
• Remove, disconnect, delete, or share only when the person asked for exactly that.
• Ask before they add an inbox that adds a paid seat. Squad first answers with the price, and the teammate adds the inbox only after you agree. See What Squad costs.
• Turn on the public dashboard, or give out its link, only when the person asked.
• Never ask for a token, key, or secret in chat. Never edit settings files on your cloud computer. Every change goes through Squad.

Switch the Reddit research tools off, and invite sam@example.com as a Viewer who works only with the writer.

Pause the support inbox and tell me what changed.

Credits

• Check the credit balance and the monthly allowance.
• Estimate the credits of a plan before they start, also when they work for an Administrator or a Collaborator. Then the estimate says what each step costs, the total, and whether it fits, but not your balance.
• Record a credit budget for one task when you give them one.

• Read the balance or set a budget when they work for an Administrator, a Collaborator, or a Viewer. Only work for the owner can. For an Administrator or a Collaborator, Squad tells the teammate to ask you in a question.
• Estimate credits when they work for a Viewer.
• Buy credits or turn on auto-recharge. Only you can, on Settings > Billing and usage.

How many credits do we have left this month?

Telegram, Discord, and Slack

• Reply to you in the chat app, and mark a question as answered when you answer it there.
• Send you a link to a page in the dashboard when you must act there, for example to approve a purchase.
• Change who may message a bot, its group chats, and which teammate answers on it, for the owner or an Administrator. See Your squad’s settings.

• Answer people who are not on the bot’s or app’s allowed list.
• Show a form card in the chat app. A form card that a teammate sends during that work starts a new conversation in the dashboard.

Questions about Squad

• Answer questions about how Squad works by reading these docs, and link you to the page. Each page they read is a Read page call.
• Give you a direct link to a screen, a task, a doc, a project, a contact, or a setting, in the names that you see.
• Read the product updates that Squad sends them, and follow them.

Where do I change which model you use?

Habits your teammates follow

Change my decision budget to 3 a day, and send the daily digest at 17:00.

What teammates cannot do in any area

• Buy credits or seats, or change your plan or your payment method.
• Connect an app through its sign-in page, add a chat bot, or connect an AI account. You do these.
• Read or change the saved value of a token, key, or secret, or ask you for one in chat.
• Pay without the card owner’s approval.
• Assign a task to you.
• Change your notification settings.
• Change a setting that the person they work for cannot change in the dashboard. See Your squad’s settings.
• Undo an action in a connected app. Squad has no undo for app actions.