docs: document posture check evaluation timing and policy distribution#774
Conversation
Add a 'When Posture Checks Are Evaluated' section to the posture checks page covering connect/login evaluation, immediate distribution of changes, and the connection-time evaluation caveat for mid-session state changes. Add a 'How Policy Changes Are Distributed' section to the access control overview covering event-driven push, no redistribution interval, and change coalescing. The two sections cross-link.
|
Warning Review limit reached
More reviews will be available in 35 minutes and 37 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
2 participants
Summary
Closes two documentation gaps that customers have asked about:
Changes
manage/access-control/posture-checks— new When Posture Checks Are Evaluated section: checks are evaluated at peer connect/login; changes distribute to connected peers immediately and apply on the peer's next connection; no periodic redistribution interval. Includes a<Note>on the connection-time evaluation model (mid-session state changes such as an OS downgrade or a stopped process are not re-evaluated until reconnect).manage/access-control— new How Policy Changes Are Distributed section: distribution is event-driven, has no fixed interval, and coalesces rapid successive changes into a single update.The two sections cross-link.
Both are same-page sections, so no navigation changes are required. Content is stated in NetBird's own voice with no external references.