> ## Documentation Index
> Fetch the complete documentation index at: https://autter.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Onboard a team

> Introduce Autter reviews and AI authorship without overwhelming contributors or reviewers.

Roll Autter out in stages so contributors understand the feedback and maintainers can calibrate the signal.

## Prepare the rollout

Before inviting the team:

* choose one active repository
* identify maintainers who can evaluate review quality
* collect a small set of standards the team already enforces
* decide whether developers will also install the Autter CLI
* review [Data and privacy](/cli/data-and-privacy) before enabling connected CLI mode

## Roll out the platform

<Steps>
  <Step title="Connect one repository">
    Follow [GitHub setup](/guides/github-setup) or [GitLab setup](/guides/gitlab-setup).
  </Step>

  <Step title="Observe default reviews">
    Let maintainers review several representative pull requests before adding many custom rules.
  </Step>

  <Step title="Add established team rules">
    Start with standards that already appear in human review comments. See [Create a custom rule](/guides/custom-rules).
  </Step>

  <Step title="Explain how to handle feedback">
    Ask authors to verify findings, review suggested fixes, and escalate uncertain behavior to a human reviewer.
  </Step>

  <Step title="Refine noisy checks">
    Change or remove rules that repeatedly flag valid code.
  </Step>

  <Step title="Expand to more repositories">
    Reuse only the rules that apply across those repositories. Keep repository-specific standards scoped locally.
  </Step>
</Steps>

## Add CLI attribution

Install the Autter CLI on developer machines when the team wants explicit AI authorship in Git history.

```bash theme={null}
curl -sSL https://autter.dev/install.sh | bash
autter status
```

Local-only mode requires no account. Connected mode can contribute attribution and prompt history to organization dashboards.

<Warning>
  Decide the prompt storage policy before a team rollout. Developers should not place credentials or sensitive customer data in coding-agent prompts.
</Warning>

## Set expectations for contributors

Tell contributors:

* Autter feedback is review input, not an automatic statement of correctness
* generated fixes still require tests and human review
* team rules should reflect documented engineering policy
* false positives should lead to rule refinement, not silent workarounds
* AI authorship comes from explicit agent attribution, not AI detection

## Measure the rollout

Use [Analytics](/features/analytics) to inspect system-level trends such as review time, pull request size, and recurring findings. Do not use one metric to rank individual engineers.