Platform · Enforce
A decision only matters if the action cannot run without it. GREENLIGHT routes held actions to the right people and gives each allowed action an execution visa the receiving system can check.
Part of GREENLIGHT
Why it matters
A decision only matters if the action that happens is the action that was decided. Enforce makes sure held actions wait for the right person, and that what finally runs is exactly what was approved.
Questions it answers
Where it sits
Every consequential action moves through the same loop. Evidence from each decision informs the next policy.
How it works
01
Actions that need approval wait, with the context a reviewer needs.
02
In the Crelis console or in tools you already use, with separation of duties and time limits.
03
An approved action is released a single time and cannot be replayed.
04
An execution visa ties the allowed action to what was decided.
What’s included
Enforce · 01
Held actions go to a reviewer with the context to decide — in the Crelis console or inside the tools you already use, such as ServiceNow and Jira.
Enforce · 02
Every allowed action carries a signed, single-use, short-lived visa bound to that exact action. The receiving system checks it before it writes.
Enforce · 03
When a business needs a temporary exception, it is requested, approved and time-boxed — never a silent bypass.
In practice
A service agent asks to change a customer’s verification phone number. The request waits for fraud operations. Once approved, that change is released once, and a second, different change would need its own decision.
Illustrative scenario.
Use case
Customer operations
Who uses it
Separation of duties is applied to every approval.
Released once, bound to the decision.
Temporary exceptions are requested, approved and time-boxed.
See it working
We connect one agent workflow in shadow mode and walk you through every decision GREENLIGHT would make, so you can judge it on your own traffic.
