# Deploying Excellent for a team

> Excellent runs on each person's Mac, set up one Mac at a time. What each Mac needs, what to set on it, where to put the rules the whole team keeps, what isn't there yet for teams, and how to reach us.

Excellent runs on each person's Mac, so a team sets it up one Mac at a time. This page is the list we work through. If you'd like our team to do it with yours,
see [Enterprise](https://www.excellent.so/enterprise).

## What each Mac needs

- A Mac with Apple silicon (M1 or later) and macOS 14 Sonoma or later.
- The agents your team uses. Excellent's live check runs in 9 of them, and it reads the logs of 6.
  [The agents it supports](https://www.excellent.so/docs/agents) has the list.

A version for Linux servers comes next, then Windows. To hear when they're ready,
[leave your email](https://www.excellent.so/download#platforms). For servers, [talk to us](https://www.excellent.so/hire/book).

Scanning is free on every Mac. The live check, the sandbox and notifications need Pro on each Mac, and team
engagements that pair with us include Pro. See [Free and Pro](https://www.excellent.so/docs/free-and-pro).

## On each Mac

**Step 1: Install it**

Get the disk image from the [download page](https://www.excellent.so/download) and drag **Excellent** into **Applications**.
[Install the Mac app](https://www.excellent.so/docs/install) has the details.

**Step 2: Read the first scan with the person whose Mac it is**

Excellent reads the agents' logs as soon as it opens and shows what it found. Each finding says which agent and where.
[Your first scan](https://www.excellent.so/docs/first-scan) says how to read it.

**Step 3: Go through the setup choices together**

Setup asks about protections that go further, each one already ticked. Some tasks may stop working with them on.
[Install the Mac app](https://www.excellent.so/docs/install) says what each one does and what may stop.

**Step 4: Press Protect My Agents**

Excellent lists what it will change before it changes anything. Then it adds its check to each agent it found, backing
up each settings file first. [Turn on protection](https://www.excellent.so/docs/turn-on-protection) has the whole list, and how to take it back
out.

**Step 5: Share the rules**

Press **Share…** so Claude Code and Codex get the same rules. Excellent shows exactly what it will write first.
[Your rules, shared](https://www.excellent.so/docs/rules).

## Pair with your team

If you have a deployment engagement, copy your pairing code from the [client portal](https://www.excellent.so/portal). In Excellent for Mac,
open **Settings → Pair with your team**, then enter the code and your account email. Click **Pair** to send them to
excellent.so along with the app's client, app version, and macOS version. Pairing is optional; it links the app to your
engagement.

The app checks the code before claiming it. When pairing succeeds, Settings shows your company and engagement
status, with **Open portal** for the latest details. **Forget pairing** removes the saved details from this Mac only;
it doesn't unpair you on our side. If the code is used or expired, ask your engagement contact for a new one.

## Rules the whole team keeps

Each agent reads its own rules file: Claude Code reads `CLAUDE.md`, Codex reads `AGENTS.md`. Rules written in a
repository's files travel with the repository, so everyone who works in it gets them, on any Mac. Rules in a person's
own `~/.claude/CLAUDE.md` or `~/.codex/AGENTS.md` stay on that Mac.

For rules the whole team should keep:

- write them in each repository's `CLAUDE.md` and `AGENTS.md`, and commit both;
- write the folders that must never be deleted and the files that must never be opened as rules, so Excellent's check
  protects them;
- on each Mac, Excellent shows which rules reach only one of the two agents. Sharing can write to each repository's
  file instead of the person's own; choose that in Settings, under Rules.

Sharing works between Claude Code and Codex. The other agents the check runs in don't get your rules from it.

## Protect main, once per repository

Branch protection lives on GitHub or GitLab, so it's set once for each repository, by someone allowed to change that
repository's settings. On the Git page, **Protect Main…** sets it after you confirm. [Git protection](https://www.excellent.so/docs/git) says
what it changes and how to undo it.

## What isn't there yet for teams

- No admin console, no settings managed from one place and no single sign-on. Each Mac is set up on its own.
- Installing or managing Excellent with a device management tool isn't supported.
- No way to send rules to every Mac from one place, beyond the repositories your team shares.
- Today each Mac keeps its own findings, so there's no view across the team yet. Seeing your team's Macs and servers
  in one view comes with [Pro](https://www.excellent.so/pricing) in January. It's planned, and it isn't built yet.

## Keep it up to date

Each Mac checks for a new version about once a day, and that can be turned off. [Updates](https://www.excellent.so/docs/updates) says what a
check sends.

## Take it off a Mac

[Remove Excellent](https://www.excellent.so/docs/remove-excellent) takes its check out of every agent and says what it leaves behind.

## Talk to us

Our team can do all of this with yours. It's priced by scope: a monthly fee for the hours of our time your team needs,
agreed in writing before the work starts, with no minimum term. [Book a call](https://www.excellent.so/hire/book) and we'll give you a price,
or email [hello@excellent.so](mailto:hello@excellent.so). Security questions and reports:
[security@excellent.so](mailto:security@excellent.so).

Source: https://www.excellent.so/docs/deploy-for-a-team
