# Pushary Team

Source: https://pushary.com/docs/agents/team
Last updated: 2026-11-01

> Set up Pushary for a team. Each person's AI agent asks that person, a rule can send risky steps to a lead, and everyone sees whose agent asked and who tapped yes.

Team is for a group of people who each run AI agents, such as Claude Code, Codex or Cursor. Each agent asks the person who runs it. A rule can send risky steps to a lead instead. Everyone sees the same record of whose agent asked and who tapped yes.

**Price:** $59 a month for 5 people, plus $12 a month for each extra person. New workspaces get 3 days free and pay nothing if they cancel during the trial. [Start the Team trial](/teams/start).

## Set it up [#set-it-up]

<Steps>
  <Step>
    ### Start the trial [#start-the-trial]

    Open the [Team page](/teams/start) and choose **Start Team trial**. Create your account, pick a handle, then check out. You land on **Overview**, which shows a **Set up your team** checklist.
  </Step>

  <Step>
    ### Connect your computer and phone [#connect-your-computer-and-phone]

    On the computer where your agents run:

    ```bash
    npx pushary@latest setup
    ```

    Scan the QR code it shows with the Pushary phone app, from the [App Store](https://apps.apple.com/us/app/pushary/id6785677563) or [Google Play](https://play.google.com/store/apps/details?id=com.pushary.app). On a Mac, you can install the [Mac app](/docs/agents/mac-app) instead, sign in, and scan its QR code.

    Then choose **Send a test question** on Overview and answer it on your phone. The computer step is done once one of your agents runs its first session.
  </Step>

  <Step>
    ### Invite your team [#invite-your-team]

    On Overview, under **Invite your team**, choose **Invite teammate**, enter the person's email, pick a **Role**, then choose **Create invitation**. Each person gets an email with an **Accept invitation** link. They sign in with that email address, then do step 2 on their own computer and phone.
  </Step>

  <Step>
    ### Send risky steps to a lead (optional) [#send-risky-steps-to-a-lead-optional]

    Open **Policies** and find **Approval routing**. Add a rule:

    * **Tool pattern:** the step to route, for example `Bash(git push:*)` for every git push.
    * **Repository:** one repository, or all of them.
    * **Route to:** a role, such as Admins, or one person.
  </Step>
</Steps>

<Callout type="info">
  Overview does not refresh on its own. Reload the page to see a teammate's progress. While **Connect your computer** is still open, choose **Check again** after your agent's first session.
</Callout>

## Who gets each question [#who-gets-each-question]

* **Each question goes to the person whose agent asked**, on their phone and in their dashboard. This starts once a second person joins. Until then, questions also go to browser push, and to Slack if you connected it.
* **A routing rule sends a matching approval to the person or role it names** instead, in the phone app and the dashboard.
* **Task updates and "finished" messages go to everyone's phone**, not only to the person whose agent sent them.

## Roles [#roles]

Every person takes a seat, viewers too.

| Role   | What they can do                                                                    |
| ------ | ----------------------------------------------------------------------------------- |
| Owner  | Everything, including changing roles and cancelling the plan. One per workspace.    |
| Admin  | Invite people and manage settings and billing. Connect agents and answer questions. |
| Member | Connect agents, answer questions and see the team record.                           |
| Viewer | See the team record. Cannot connect agents or answer questions.                     |

Owners, admins and members can all change policies and routing rules. Viewers cannot.

## Seats [#seats]

* 5 seats are included, and yours is one of them.
* An invitation holds a seat until it is accepted or expires after 7 days.
* When no seats are left, you cannot invite anyone until you add one. On an older 10-person Team plan, contact support instead. Open **Settings > Subscription**, choose **Manage seats**, then **Review change** and **Confirm seat change**. Each extra seat is $12 a month. Stripe charges the prorated amount right away, and nothing during the trial.

## See what happened [#see-what-happened]

**Team activity**, in the sidebar, lists your team's questions and the actions their agents report, for the last 7 or 30 days. Each row shows whose agent it was and whether an answer was recorded. Choose **View details** to see who answered.

**Sprint record** opens from **Engineering sprint view** at the bottom of Team activity. For each sprint, two weeks unless an owner or admin changes it under **Sprint calendar**, it shows sessions, questions and commits, **Worth a look** items such as a very fast yes on a risky step, a view by person and by repo, and **Copy for retro**. Export it as CSV or JSON from **More**.

The owner and admins get the sprint record by email on the sprint's last day. It is not sent during the trial.

Everyone in the workspace sees the same pages. Nobody is scored or ranked.

## What the record does not show [#what-the-record-does-not-show]

* **Who said yes at the agent's own prompt.** Team activity can show that a step was left to the terminal, and the action if the agent reports it, but not who said yes.
* **Who answered from a web link.** Answers given in the Pushary phone app, Mac app or dashboard carry the person's name. Answers from a web link do not.
* **Steps your rules approve on their own.** They run without a question, so Team activity leaves them out.
* **Full commands.** Actions are the shell commands, file edits and commits an agent reports. A command shows its first two or three words, such as `git push`.
* **Anything before a person connected.** Each person's record starts when their agent first connects.

## Good to know [#good-to-know]

* A routing rule has **Only they can answer** on by default, so Pushary refuses an answer from anyone else. The person whose agent asked can still answer at their own agent's prompt, and that answer is not recorded.
* Routing rules match tool approvals only. A question an agent writes itself always goes to the person whose agent asked.
* The approval mode (When away, Always, Alert only or In agent) is set on the workspace's rules, not per person. Everyone on the team gets the same mode, and a change by anyone who can edit policies applies to all. New workspaces start on **Always**. See [the four approval modes](/docs/agents/policies#the-four-approval-modes).
* The phone app cannot approve risky steps such as `rm -r`, a force push or a deploy. It can deny them. Approve them in the dashboard, or at the agent's own prompt, where the yes is not recorded.
* Already connected to another workspace? In the Mac app, open **Settings**, then **Account**, then **Change workspace**. In the terminal, run `npx pushary@latest login --force`, pick this workspace, then run setup again in a new terminal.
* A Team plan covers one workspace and keeps 365 days of history.
* Paying through the App Store or Google Play? [Contact us](mailto:business@pushary.com) to move to Team. Web checkout opens only after the store subscription ends.

## Billing [#billing]

Open **Settings > Subscription**. **Manage billing** opens Stripe, where an owner or admin changes the card or downloads invoices. **Cancel plan** is for the owner and cancels at the end of the billing period.

## Related [#related]

* [Permission policies](/docs/agents/policies)
* [Audit trail and export](/docs/agents/audit-log)
* [Quickstart](/docs/agents/quickstart)
* [Mac app](/docs/agents/mac-app)
* [Plans and limits](/docs/pricing-and-limits)