Approval policies

Create a policy draft

Choose New approval policy, enter a policy name and optional description, then choose Create policy draft. The new record begins as an editable draft with a first approval level. It is unpublished and does not assign, request, or complete an approval.

Set approval levels and applicability

Build the levels in their displayed order. For each level, choose whether Any one target or All targets must respond, add the applicable targets, and choose either Always or Amount is at least for the level condition. Set the self-approval choice and the rejection action as needed.

Use named people only when they are offered by the authorized organization directory. Use a product-qualified role when responsibility belongs to an eligible role in the selected product context. Do not use copied identifiers or assume that a role from another organization is available.

Set deadlines, reminders, and escalation

For a level, choose the supported deadline and reminder timing, then add an escalation target and timing when needed. These values describe the draft’s intended future behavior. In Phase 1 they do not start a timer, send a reminder, send an escalation, or deliver a notification.

Save explicitly

Edits are local until you choose Save policy draft. Saving records a new policy-draft revision and rechecks validation. An incomplete-but-safe policy may save with validation issues so it can be completed later; malformed or unsafe input is rejected instead of being saved.

Use reference counts carefully

Each policy entry reports how many current workflow drafts reference that policy. A workflow editor can select only a saved valid policy draft. The workflow records that policy revision for readiness, so changing a policy later can leave a referenced workflow pointing to an older policy revision.

Resolve a policy conflict

If a policy draft changed elsewhere before you save, RS1 keeps your local edits and presents three choices: Reload latest saved revision replaces local state with the latest saved revision, Keep local copy retains local state for manual comparison, and Cancel closes the choice without changing local state. Save again only after resolving the difference.

Refresh safe-test evidence after a policy change

Saving a policy change makes related safe-test evidence outdated. Return to the related saved workflow draft, review its policy reference and validation, then run a new synthetic safe test and Check readiness. This does not execute the workflow or contact an approver; it replaces authoring evidence only.

Phase 1 boundary: Authorized accounts can use policy authoring in Preview. Policy drafts, templates, safe tests, readiness, and inactive soft archive are authoring only; Publish and the final three Workflow Settings sections are future or disabled. Production remains disabled until UAT is complete.