Skip to content

docs(policies): clarify root quorum bypasses time-based policies #809

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tkhq-valet-dev wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(policies): clarify root quorum bypasses time-based policies #809

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions features/policies/time-based-policies.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,10 @@ Like the `consensus` and `condition` fields, the `time` field must evaluate to a
The **trusted server time** is NOT a client-supplied timestamp and cannot be spoofed by the caller.
</Note>

<Note>
**Root quorum bypasses time-based policies.** Root quorum approval is checked before policy evaluation, so a request that meets root quorum completes without any `time` field being evaluated. Time windows only gate requests that have not met root quorum. See [Root quorum](/features/users/root-quorum) for the full bypass rules.
</Note>

The `time` field (like the `condition` and `consensus` fields) is optional. When it is absent or an empty string, the policy is always active with respect to time. When it evaluates to `true`, the policy is active and participates in evaluation as usual. When it evaluates to `false`, the policy is skipped entirely for that request: it neither allows nor denies, and does not participate in the outcome. Such a policy is reported with the `OUTCOME_TIME_INACTIVE` policy-evaluation outcome.

<Note>
Expand Down Expand Up @@ -150,3 +154,7 @@ The `time` field composes with the other two fields at the policy level: a polic
```

Outside the business-hours window the `time` field evaluates to `false` and the policy is skipped, so the same signing request is no longer allowed by this policy.

<Note>
A `time` field does not restrict when a root quorum member can approve. If a request accumulates enough root approvals to meet the root quorum threshold, the activity completes even when those approvals arrive outside the window, and even when a non-root approver voted inside the window as part of the same request. Use non-root users with scoped policies when a time window must actually bound approval.
</Note>