Skip to content

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

Open
tkhq-valet-dev[bot] wants to merge 1 commit into
mainfrom
docs/time-based-policies-root-quorum-note
Open

docs(policies): clarify root quorum bypasses time-based policies#809
tkhq-valet-dev[bot] wants to merge 1 commit into
mainfrom
docs/time-based-policies-root-quorum-note

Conversation

@tkhq-valet-dev

@tkhq-valet-dev tkhq-valet-dev Bot commented Sep 3, 2026

Copy link
Copy Markdown

Summary

Root quorum is checked before policy evaluation, so approvals that meet root quorum complete an activity even when the request is outside a time-based policy's active window. The time-based policies page didn't call this out, which came up recently in #eng-policies as a documentation gap.

Scenario the notes now cover

  • Policy configured: active only 9 AM–5 PM, requires 2 approvers.
  • One non-root user votes during business hours.
  • Root quorum member votes at 6 PM.
  • Activity completes: root quorum was met, so the time constraint never applied.

Changes

features/policies/time-based-policies.mdx — added two <Note> callouts:

  1. After the intro, alongside the existing trusted-server-time note. Establishes the bypass rule up front and links to /features/users/root-quorum.
  2. At the end of "Combining time with consensus and condition". This is where a reader is most likely to design a scoped rule like "ops team during business hours" and forget that a root member's vote will still land the activity. Also gives the practical guidance: use non-root users with scoped policies when a time window must actually bound approval.

No other pages touched. No behavior change — documentation-only.

Root quorum is checked before policy evaluation, so approvals that meet
root quorum complete an activity even when the request is outside a
time-based policy's active window. Add two notes to the time-based
policies page:

- After the intro, alongside the trusted-server-time note, so readers
  learn the bypass rule up front.
- After the combined consensus/condition/time example, where a reader
  is most likely to design a scoped rule like 'ops team during business
  hours' and forget that a root member's vote still lands the activity.
@mintlify

mintlify Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
turnkey-docs 🟢 Ready View Preview Sep 3, 2026, 9:24 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@grahamritter grahamritter left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant