Team access
Assign community responsibilities through capabilities and permissions instead of relying on broad role labels.
Team access should answer what a person can do, not merely what their title sounds like.
A Space may need separate responsibilities for:
- membership and invitations;
- Mission authoring and publishing;
- submission review;
- dispute moderation;
- reward funding;
- Sponsor terms and evidence;
- insights and exports.
Give each teammate only the capabilities needed for their work. A reviewer does not automatically need control over funding. A Sponsor contact does not automatically need access to Member proof.
Keep sensitive actions deliberate
Changes to team access, reward funding, moderation outcomes, or Sponsor terms should create an auditable record. High-impact actions can require stronger approval.
Review access when a teammate changes responsibilities or leaves. Avoid shared accounts: individual access makes decisions attributable and recovery possible.
ZYNC’s internal authorization model checks explicit permission for each action. The product experience should express that model in practical language so teams can reason about access without learning the implementation.