SupraOS
Explore demos Talk to us
AUTHORITY AND VERIFICATION

Define the decisions
SupraOS may act on.

Set which actions need a named approver, which may proceed within an accepted policy and what conditions stop execution. A changed plan carries a fresh authority check.

Trust Center
AN APPROVAL WITH A BOUNDARY

Account A. One entitlement.
One approved version.

The owner approves an entitlement change for Account A. If the scope changes to Account B or the terms change, the original approval no longer applies.

Test the boundary in the demo
Permitted action
Update the agreed entitlement on Account A
Approval
Named owner · exact plan version
Changed account or scope
Hold and request approval for the revised plan
Independent check
Read Account A's entitlement from the destination
Result
Customer acceptance, followed by a later check
01

Bound the permitted action

Define the account, object, action, scope, resources, conditions and authority relevant to the work.

02

Keep material changes visible

A change to the approved plan or an important condition requires a new decision. Existing approval does not authorize a different commitment.

03

Inspect the destination independently

Separate the execution response from the evidence of the resulting state. A mismatch keeps the affected outcome open.

04

Continue observing the result

Customer acceptance and later observations determine whether the result holds. A reversal reopens the affected work.

Review the proposed boundary.

Contact the security team with your company, deployment and the materials you need.

security@supraos.co