Scope model
- Use org-wide threads for updates relevant to all leadership members.
- Use board-only scope for governance-sensitive topics.
- Use team scope when discussion context should stay within a specific operating team.
Discussions · Permissions
Discussion permissions and participation
This deep dive explains how to choose scope and manage participants so discussion access stays aligned to governance needs.
Participant management
- Add participants when they are decision makers, responsible owners, or unblockers.
- Remove participants when the topic scope narrows or confidentiality changes.
- Keep participant lists small to reduce notification noise and improve response quality.
Operational safeguards
- Avoid mixing unrelated topics in one thread. Start a new discussion when context changes.
- Post explicit outcomes and owners at thread closure to reduce ambiguity.
- Review unread-heavy threads weekly and rebalance participation if needed.
Related board software topics
Use these pages to connect this workflow to broader board portal, meeting software, decision tracking, and governance requirements.
Understand where each guide workflow fits in a full board portal implementation.
See how agenda, invites, and minutes processes map to board meeting software needs.
Connect guide playbooks to decision ownership and execution tracking.
Review governance and compliance expectations tied to board operations.