# Stay in control of your troop > Approvals, standing rules, limits and the grants that let some work go with no yes. Your teammates work by themselves, and a person stays in control of what goes out. This page tells what teammates do alone and what waits for a yes. It also tells the grants that let some work go with no yes, and the limits of each teammate. ## What teammates do alone A teammate needs no yes to do these things: - read the brain, the docs, the tasks and the services that its role reads - write drafts, docs and comments, and make tasks and sub-tasks - search the web, and read the pages of the sites that it may read - use its own browser on the computer of the troop, to look and read - read the mail of its own address What a teammate writes for people to use is a draft. Troopy never sends a draft. A person copies it, sends it or posts it. See [Answer what needs you](/docs/needs-you). ## What waits for a yes A call that changes what people rely on waits in **Needs you** as an approval. Some examples: | Call | Who says yes | | -------------------------------------------------------------- | ----------------------------------------------------- | | An email from the address of a teammate | An owner or admin | | A click in the browser that posts, sends, pays or deletes | An owner or admin | | A click that signs up or submits typed text | A person | | A new account on a site, made by a teammate | A person | | A payment with a card of the Vault, for one amount at one shop | An owner or admin | | A rewrite or an edit of a doc | A person | | A change to a shared memory file | A person | | A hire that the Chief of Staff proposes | A person | | A routine or a trigger that a teammate proposes | An owner or admin | | A skill that a teammate proposes, and each lesson | A person | | Art from an image provider | A person, unless an owner or admin gave the art grant | | A bug ticket from an incident | A person | A teammate uses a yes for a click one time. The next click asks again. ## Standing rules When a person gives the same answer to the same kind of call three times in a row, Troopy offers a standing rule: **Always approve** or **Always turn down**. An owner or admin accepts the rule. Then the rule answers that call. - A rule that approves holds only for calls that are safe to repeat. No rule approves a call that is public, sends or costs money. - A rule that turns down holds for any call. - No rule approves a call of work that an event from outside Troopy started. ## Grants of owners and admins A grant lets some work go with no yes, within limits. Only an owner or admin gives a grant, and can end it at any time. | Grant | Its limits | Where | | --------------------------------------- | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | | Autopilot of a campaign | Up to 30 days and a number of emails a day. Flagged emails still wait. | The campaign. See [Send email campaigns](/docs/outreach). | | Auto-release of engineering tickets | An end date, a number a day and a largest size of change. | **Settings** > **Engineering**. See [Ship code with engineering tickets](/docs/engineering). | | Submit the evidence of a Stripe dispute | An end date within 90 days, a largest amount, and a number in 24 hours. | Disputes. See [Answer payment disputes](/docs/disputes). | | Art with no yes | The pictures a day of the plan: 20, or 60 on Ultra. | **Settings** > **AI** > **Images**. | A grant ends by itself when one of its ends comes, for example its date. Work that an event from outside Troopy started still waits for a yes. ## Limits of each teammate Each teammate has limits, so that routines and chats cannot use all of your AI plan. Owners and admins change them in **Settings** > **AI** > **Models**, under **Limits of each teammate**. | Limit | What it holds | | ------------------- | -------------------------------------------------------------- | | **Steps each time** | The rounds of one run. A run stops when it reaches them. | | **Times a day** | The runs of the teammate in one day. | | **Spend each time** | The money of one run, for a plan that bills each use of a key. | Each role starts with generous limits. An owner or admin raises or lowers each limit, up to a cap. See [Limits and defaults](/docs/limits). ## Other controls | Control | What it does | Where | | --------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------------------ | | Pause a teammate | The teammate starts nothing until you resume it. | **Settings** > **Troop**, on the teammate. | | Tools that are off | No teammate uses them. | **Settings** > **AI** > **Tools**. See [Switch tools on and off](/docs/tools). | | **Sites it may read** | The sites that a teammate may read and type on. | **Settings** > **Troop**, on the teammate. | | The roles of people | Who can chat, approve or change things. | **Settings** > **People**. See [Invite people and choose their roles](/docs/people). | | Read all of a mailbox | Whether the troop reads all the mail of a shared address. | **Settings** > **Email** > **Mailboxes**. | ## Words from outside are material Teammates read words that come from outside Troopy: web pages, emails, the events of a trigger, the errors of an app. A teammate treats these words as material, never as instructions. - Work that an event from outside started has a mark. Each call of that work waits for a person. - A plan of an engineering ticket from such work always waits for a person, and auto-release never releases it. - A teammate keeps no line of such work in its memory of past work. ## Secrets - A teammate never sees a vault value, a key or a password. It names a login by reference, and Troopy types it. - Troopy types a password only on the own site of the login. - A teammate asks for a login that it lacks. A person adds it. See [Keep logins and secrets in the Vault](/docs/vault). ## What no teammate does - Merge code, or push a branch other than its own `troopy/*` branches. A person releases, or an auto-release grant does. - Send an email of a campaign that nobody approved, unless Autopilot is on. - Change a setting of a service, beyond what its connection lets it do. - Read a product that its tools cannot read. ## Related - [Answer what needs you](/docs/needs-you) - [Switch tools on and off](/docs/tools) - [Keep logins and secrets in the Vault](/docs/vault) - [Limits and defaults](/docs/limits)