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

# Built-in presets

> Role boundaries for Full Control, Spec, Executor, QA, Validator, Reporter, and Sprint Manager.

# Built-in presets

You can use built-in presets to give agents a role without hand-selecting hundreds of flags. Presets are source-defined permission sets; board overrides can restrict them further.

## Preset matrix

| Preset         | Enabled flags | Role boundary                                                                                                                                                                                                     |
| -------------- | ------------: | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Full Control   |           270 | All permissions active — unrestricted access.                                                                                                                                                                     |
| Executor       |            78 | Implement normal cards. Moves not\_started→validation. Cannot submit gates or promote validation→done.                                                                                                            |
| Validator      |            99 | Exclusive gate-holder. Submits spec/task/sprint validations and evaluations. On cards, only touches validation status.                                                                                            |
| QA             |           106 | Owns test scenarios and test card lifecycle. No gate submissions.                                                                                                                                                 |
| Reporter       |            85 | Observador — lê tudo, abre bug card, pergunta e vota em choice. Zero submit de gate, zero edit, zero consolidação KG. Ideal para PO/stakeholder/onboarding.                                                       |
| Sprint Manager |            89 | Dono do ciclo de sprint (create → active → review → closed + evaluation). Lê contexto de spec/refinement/ideation e orquestra assign de cards. Não cria cards nem submete gates técnicos. Coexiste com Validator. |
| Spec           |           205 | Defines the spec (ideation→refinement→spec content, sprint plan, card breakdown). No gate submissions, no card execution.                                                                                         |

## Full Control

Full Control has every current flag enabled. Use it for solo development, local evaluation, or trusted operators. Do not use it as the default for multi-agent boards because it removes role separation.

## Spec

Spec owns ideation, refinement, spec content, sprint planning, and card breakdown. It does not submit validation gates. Use it for the agent that investigates and writes the contract.

## Executor

Executor implements normal cards. It can move card work through `not_started -> started -> in_progress -> validation`, but it cannot submit task validation or promote validation to done.

## QA

QA owns test scenarios and test-card lifecycle. It reads specs, asks questions, and manages test evidence, but it does not submit validation gates.

## Validator

Validator is the exclusive gate-holder. It submits spec validation, sprint evaluation, and task validation. On cards, it only operates in validation status and routes work to done or back for rework.

## Reporter and Sprint Manager

Reporter is read-heavy and useful for stakeholders or status agents. Sprint Manager owns sprint lifecycle and coordination without taking over implementation or validation.

## Choosing the right preset

| Situation                                  | Preset          |
| ------------------------------------------ | --------------- |
| One trusted local agent doing everything   | Full Control    |
| One agent writes specs, another implements | Spec + Executor |
| A separate reviewer must approve work      | Add Validator   |
| Test evidence is a separate lane           | Add QA          |
| Stakeholder wants read-only visibility     | Reporter        |
| Delivery lead manages sprint flow          | Sprint Manager  |

<Note>
  Gate submission is intentionally concentrated in Validator. If Executor can submit its own validation, validation becomes another status label instead of independent evidence.
</Note>

## Related pages

* [Permission model](/permissions/model)
* [Custom permissions](/permissions/custom)
* [Validation gates](/concepts/validation)