⚖️ Governance
Governance decides whether a reveal may happen. Every gate your plan enables applies; none replaces another. Which gates a plan uses is set in its Plan properties.
| Gate | Question it answers |
|---|---|
| Access policy | Is this member authorised right now, through their teams and roles? |
| Dead Man Switch | On Business Continuity plans: is the plan's creator still there? |
| Authentication | Is the requester really who they claim to be? |
| Moderation | Do the appointed moderators approve this request? |
Only when every applicable gate passes does the reveal proceed. And a plan is never unguarded: every configuration keeps moderation, authentication, or both.
What a request looks like
- A member requests access to a plan.
- The access policy checks their membership live, through teams and roles.
- On continuity plans, the Dead Man Switch gives the creator the chance to stop it.
- Authentication confirms the requester, where required.
- Moderators approve or deny, where configured.
- Only then do the shares come together, on the requester's own computer.
For your team this means access is never a favour someone grants over chat. Requests follow one path, every decision is made on a trusted device, and each step lands in the audit trail: who asked, who approved, what was revealed and when.