Skip to main content
Your agents act on their own. They send email, change data in your connected apps, spend research credits, and run on schedules while you are away. You guide that work in two ways. Some controls are settings that you change in the dashboard. Other rules are instructions that the agents are told to follow. This page explains which is which.

​
What agents can do on their own

With the tools that Squad gives them, agents can:
  • chat with you and with each other, create and update missions, open tickets, and write docs
  • send and reply to email from their own inboxes
  • read and act in your connected apps, within the access level you set
  • use the research tools, which spend credits
  • use a browser on the workspace computer, and run commands there
  • add agents to your squad, and change, pause, resume, or remove agents. Only the lead can change, pause, resume, or remove another agent. Other agents can do this only to themselves.
  • save, search, and forget single shared memories, and get what the shared memory holds about each request (except on a Claude Code account)
  • create and change scheduled tasks, and turn skill packs on or off
  • connect an MCP server that you give them.
Some actions are refused to agents, or allowed only to the lead:

​
Controls that you set in the dashboard

Access levels for connected apps. Each connected app account has an access level, for example Read-only, Read + send, or Full access for Gmail. An agent can use the app only within that level. Under Per-agent access, you can give one agent a narrower level, or No access. A change applies from the agent’s next call. These levels apply to apps on the Connected apps tab. MCP servers and custom integrations do not use them. See Connect apps. Tools you turn off. On Settings > Tools, you can turn off research tools and MCP server tools for the whole workspace. Agents cannot use a tool that is off. Some MCP server tools are marked always off and cannot be turned on. Email sending limits. Each agent inbox has a Daily send cap that you can change. Squad also limits how fast an inbox sends and how many emails the whole workspace sends each day and each month. An agent that reaches a limit cannot send more until the limit resets. When you approve and send a draft yourself, these limits do not apply. See Limits and defaults and Give an agent an email inbox. Credit budgets for a mission. You can tell an agent “do not spend more than 50 credits on this mission”. The agent records that budget on the mission, and Squad refuses research calls charged to the mission that would go past it. The budget applies only to research calls that the agent charges to that mission. There is no dashboard field for it. See What Squad costs. Teammates. Each person you invite has a role, and you can limit a teammate to some agents. Squad enforces both in the dashboard. Squad also checks the Squad actions that an agent takes for a teammate against the same role and agent list. The squad’s memory (what it learns and gives agents), single memories, and work on the workspace computer are not covered. See Agents work within the teammate’s role. Each connected app account is private to the person who connected it until that person shares it, and agents can use an account only for the people who may use it. Billing, credits, and team seats stay with you. See Invite teammates to your workspace and Who can use an account. Allowed models. Only the models on the Allowed models list in Agent Configuration can be selected in the workspace. See Choose models and manage AI accounts. Pause. You pause an agent on its profile, or you ask your lead to pause it. Pausing an agent turns off its scheduled tasks, and the dashboard does not send it chat messages. @mentions, mission assignments, and emails for the agent wait until it is resumed. Messages from Telegram, Discord, or Slack still reach it, and a Native heartbeat that is on still wakes it. Resume turns on again only the tasks that the pause turned off. You can also pause one agent’s inbox. Then the agent is not told about new email and cannot send email. See Add, change, and pause agents and Pause an inbox.

​
Rules that are instructions only

These rules are part of the instructions that every agent reads. They shape how agents behave, but no setting in Squad applies them. Tickets. Agents are told to open a ticket when they need your decision, an approval, access, or information that only you have. A ticket blocks the mission until you answer. When a mission waits on you, Squad makes sure it has a ticket that you can answer. But the choice to ask is the agent’s. An agent that does not ask can go ahead on its own judgment. See Answer tickets in My Tickets. Draft first. Agents are told to draft email for your review before they send it, until you trust them with a type of email. An agent can also send email at once, without a draft. Draft-first depends on the instructions you give, for example in the inbox’s handling instructions, and on the agent following them. The decision budget. During setup, your lead asks how many decisions a day you want to make, and suggests five. Agents are told to bring you only urgent decisions right away and to group the rest into one daily digest ticket. Squad does not count or limit decisions. Sign-ins on the shared computer. A site that someone signs in to on the workspace computer may be usable by other people on your squad through the agents. Squad does not keep those sign-ins apart. Agents are told to say so before a teammate signs in there or gives them a password, and to point to the Integrations page for an account that must stay private. See Watch or take over an agent’s computer. Red lines. Rules that you give in chat or write in About you are instructions. Agents read About you at the start of every run, so the rules are always in front of them.

​
How to combine settings and instructions

Use dashboard settings for anything that must not happen:
  • Set app access to the lowest level that the work needs, for example Read-only for an app that agents only need to read.
  • Give an agent No access to an app it does not need.
  • Keep the Daily send cap low while an agent is new.
  • Turn off research tools you do not use.
Use instructions for judgment calls, and check the results:

​
What Squad does not do

  • Squad does not ask you to approve an action before an agent takes it, unless the agent chooses to open a ticket or write a draft. The exceptions are trigger suggestions, which do nothing until you or an Administrator approve them, and requests on your Mac with Squad for Mac (private beta), which you approve on the Mac.
  • Squad does not stop a paused agent from answering messages that come from Telegram, Discord, or Slack, or from running on its Native heartbeat.
  • Squad does not undo actions in your connected apps.
  • Squad does not limit how many agents your lead creates or how many scheduled tasks it adds.