Loading…
Execution pattern
Privileged access grant
Grant the narrowest scope that works, and expire it.
What executes
An access request grants elevated or root scope to a person, contractor, or service.
What normally goes wrong
Access is granted broadly because narrow is slow, and revocation depends on someone remembering. Standing privilege accumulates until it is the incident.
The decision
The signals available at the moment of the action, and the rule that judges them.
Signals
- Scope requested versus scope needed
- Duration and whether expiry is set
- Employment or contract status
- Whether the approver is independent of the requester
The gate
Refuse standing privilege where just-in-time access would serve, and refuse any grant without an expiry.
ALLOW
Access is granted, scoped and time-boxed.
ESCALATE
A broad or long-lived request waits on the resource owner.
BLOCK
The grant does not happen — for example root scope to a contractor.
Four stages left to right. Input signals — user or agent identity, context and data, tools and resources, spend and budget, policies, history and reputation, and environment — enter the Decionis Protocol. Inside, the protocol normalizes context and intent, evaluates policies and rules, runs a deterministic risk and policy engine, and explains the reason and evidence. It emits a verdict: ALLOW (authorized), ESCALATE (needs approval or more info), or BLOCK (high risk or out of policy). The verdict drives an enforcement action: allow, block, require approval, or throttle and limit. Every decision is recorded for audit, learning, and continuous improvement.
6 policies implement this pattern
Fork one and change the thresholds. Available today on 3 platforms.
ServiceNow Just-In-Time Access
Temporary admin rights get a timed dossier and a revocation trail — so the grant expires whether or not anyone remembers.
servicenow
IT Ops Pack
Access, change, and procurement gates for internal automation — prove every sensitive change followed the approved path.
servicenow
Workday Offboarding Access Guard
When a termination event lands, prove access and payroll were actually revoked — not just ticketed.
workday
HIPAA-Grade Access Change Gate
Privileged-access and production-change controls for ServiceNow ITSM — proving every change followed the approved path.
servicenow
HR & People Ops Pack
Fairness, approval-chain, and offboarding gates — prove every hire, promotion, and termination cleared its checks.
workday
SaaS Ops Pack
Cloud spend, discount, and entitlement gates — stop runaway burn, margin leakage, and unsupported entitlement changes.
sdk
Related concepts
This pattern is one answer to each of these.
What to do next
The same five steps for every pattern in the library.
- Simulate this recipe
Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.
- View the signed Decision Dossier
See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.
- Deploy in shadow mode
Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.
- Connect a real workflow
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
- Share the verified result
Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.