Use this reference to arrange the exact authority for a requirement and its native release. Automation access and the source product's current grants are separate checks. A centrally approved requirement does not create permission to read another site, edit an unsupported target or perform physical work.
Read the permission terms
OR means either listed Automation role is sufficient for that central role check. AND means both permissions are needed for a combined responsibility. Each native action also needs the source product's current role, site and realm authority. Another person means an eligible individual absent from the relevant contributor set.
Recent verification means an Accounts second-factor check within the last five minutes where required. The original actor, exact source, current assignment and recovery generation remain part of authority. Existing successful receipts retain their history; they do not renew permission for a new change.
Match the task to its authority
| Task | Who | Additional conditions | Related guide |
|---|---|---|---|
| Open the requirement list | Any of the six Automation roles | Correct organisation and site. A listed revision is not evidence of native activation. | Requirements and plans |
| Open requirement detail | Owner OR Author OR Reviewer OR Supervisor OR Viewer | Operator alone has list access, not this detail authority. | Operator |
| Create or revise a requirement | Author | Current requirement revision and complete intended behaviour. Saving changes no production rule. | Requirements and plans |
| Read a working plan or native workspace | Author OR Reviewer OR Supervisor OR Viewer | Owner alone does not inherit this working access. Protected native reads additionally require current product access. | Product context |
| Prepare/save a working plan or capture its source context | Author | Exact requirement revision and explicitly selected source contexts. Preserve unanswered questions and unsupported actions. | Requirements and plans |
| Read shared classification or validity definitions | Author OR Reviewer | This definition workspace has narrower reading roles than requirement detail. | Shared classifications |
| Edit a native draft or adopt a proposal | Author | Source-product authority for that exact operation and revision. Product phase and complete-document constraints still apply. | Native drafts |
| Supply or revise native independent cases | Author | Complete independently established expectations. The product retains case-set identity and contributors. | Independent cases |
| Independently review native cases | Reviewer | Recent verification and the source product's case-review authority and independence checks. | Independent cases |
| Create a native candidate | Author | Product-specific prerequisite reviews, frozen case set and exact current draft. | Proof and release |
| Run native verification | Author OR Reviewer | Correct candidate and frozen evidence; the product can impose further requirements. A verification record is not publication. | Proof and release |
| Submit a complete native release | Author | Current whole release, contributors and dependencies. Native submission and central submission are distinct. | Proof and release |
| Record native release review | Reviewer | Recent verification; exact submission and the native product's contributor rules. | Proof and release |
| Submit for central review | Author | Exact current requirement revision and complete qualified native release manifest. | Proof and release |
| Record central review | Reviewer | Recent verification; cannot be a release contributor. Decision and explanation must match the exact native reviews. | Proof and release |
| Prepare or activate a reviewed native release | Reviewer | Recent verification, current native grant and readiness, exact reviewed content and dependency/recovery evidence. Preparation is not activation. | Activation and recovery |
| Inspect an original retained native/rollout outcome | Author OR Reviewer OR Supervisor OR Viewer | Current permitted read and original request identity. Checking reads that outcome without sending its effect again. | Activation and recovery |
| Create a bounded product configuration from a plan step | Author | Recent verification and the native action's grants; exact retained plan, selected source and supported action descriptor. This does not complete later physical work. | Plan step actions |
| Create a shared definition or save/verify its expected examples | Author | Complete independently chosen facts and expected answers; verification is separate from review. | Shared classifications |
| Review or withdraw a shared definition | Reviewer | Recent verification. Review excludes relevant definition and case contributors and uses exact proof evidence. | Shared classifications |
| Map a reviewed definition or validity rule into a product | Author | Exact reviewed definition AND current native source context, complete mapping and permitted slot. Native independent publication remains required. | Definition mappings |
| Read coordinated policy sets | Author OR Reviewer OR Supervisor OR Viewer | Current permitted site and retained exact set membership. | Policy sets |
| Compose a coordinated policy set | Author | Exact anchor requirement and complete member release/submission identities. | Policy sets |
| Review a policy set and prepare/open each member | Reviewer | Recent verification, independent set review and current member readiness. Each member operation has its own result. | Policy sets |
| Download site records | Owner OR Supervisor | Real-site scope and recent verification. The export does not replace product-owned operational evidence. | Records and practice |
| Administer setup and access | Owner | Current organisation administration; Author or Reviewer must be granted separately for their work. | Owner |
Arrange both authorities and independent people
An engineer authoring through Automation needs its Author role AND the source product's permission for the proposed native action. A reviewer similarly needs central Reviewer AND the required native review/activation grant. Holding Owner in either product does not silently supply those working roles.
A person who contributed to the draft or expected results cannot satisfy that release's independent review by switching roles. Check the product's complete contributor evidence. Practice work also uses current real-site grants and a matching sample realm; it does not expand every user to every role.
After an interrupted answer, preserve the original request and use the relevant outcome check. Do not create a replacement command or paid proposal merely to obtain a fresh answer. Approved operational rules continue in their owning product and do not need a model to decide each event.