Exceptions, overrides and approvals¶
Every rule meets a case it shouldn't stop: a customer contract that needs one key on the old model, a launch that can't wait for next month's budget. Without a named way out, people loosen the rule for everyone, or share a key that isn't covered. Vidai gives each exception a name, a reason and an end, records who asked and who agreed, and makes sure nobody widens their own access without a second person seeing it.
Three ways out of a rule¶
| Kind | What it lifts | For how long |
|---|---|---|
| Exemption | One key let off a required routing rule or a guardrail | Until an optional end date |
| Emergency override | A budget, a guardrail, or every guardrail part of a whole policy, for one key or everything it covers | 1 to 24 hours; it ends by itself |
| Extra models for one person | A model beyond what their team allows, with a reason | Until an optional end date |
Some things are never lifted: an emergency override never lifts a compliance route or the approved destinations, a compliance route can't be exempted from, and rate limits aren't lifted by an override. A whole policy lifted still keeps its region rules in force.
Policies › What applies here › Exceptions lists every exemption and override in force, each with its reason and its end. A key's page lists Exceptions for this key.

Who asks, who approves¶
flowchart LR
GA[Group admin] -->|Ask to lift for up to 24 hours…| Q[Approvals]
Q -->|budget override| F[Organisation admin<br/>or Finance]
Q -->|guardrail override| C[Compliance officer, or anyone<br/>given the right]
F --> Live[Override starts,<br/>recorded with who approved]
C --> Live
OA[Organisation admin] -->|Lift for up to 24 hours…| Self[Starts at once,<br/>marked Self-approved]
- Organisation admins lift a budget or guardrail at once in an emergency. Their own override is recorded as Self-approved, in the list and in the audit log.
- Group admins ask, for their own teams. Nothing is lifted until someone who may decide that kind of override approves it: budget overrides by organisation admins and Finance, guardrail overrides by Compliance officers. An organisation admin can give either right to anyone, themselves included. On Community, where there is no Compliance officer, guardrail overrides are decided by the people an organisation admin has given Approve guardrail overrides.
- Exemptions from a required rule granted at the level that set it apply at once; otherwise they wait for a second admin.
Changes that wait for a second admin¶
Some changes widen someone's own reach, so they wait on Approvals for another admin: adding yourself to a team, giving yourself a role, giving a service account a role, moving a team between admins. Nobody decides their own request: under Asked by you you can only cancel it.
A sole admin is never stuck. While an organisation has only one organisation admin, changes that would need a second admin's approval go ahead, and Home suggests Add an organisation admin.

How it's recorded¶
Every exemption, override and approval keeps who asked, who decided, the reason and the times, in the audit log. While any override is live, a notice says so on every page; End now… ends one early, and what it lifted applies again straight away. Overrides and approvals go into the evidence pack as oversight.
Related¶
- Rules at levels
- Budgets · Guardrails · Routing and fallback
- People and roles: Finance, Compliance officer and the approve permissions
- Model access: extra models for one person