Meeting Note supports structured team roles so access can be assigned intentionally: Owner, Manager, Team Lead, Member, and Spectator. These roles are used to control who can manage team settings, who can run day-to-day meeting operations, and who should remain read-only.
Team-level member administration is owner-governed. In practical terms, owner-level controls cover actions like updating member roles, removing members, and managing invitation-code workflows. This keeps high-impact access changes centralized and auditable instead of spread across every contributor account.
Not necessarily. Meeting Note supports an approval-based flow where join-by-code can create a pending join request that must be approved before full membership access is granted. This allows teams to use shareable invite paths without losing admission control.
No. Spectator access is intentionally restricted for read-only collaboration. Creation and management actions are reserved for higher-permission roles, so teams can include observers/stakeholders without exposing operational controls.
Meeting Note includes ownership safety guardrails to prevent destructive ownership states (for example, removing or demoting the sole remaining owner). That protection helps ensure teams don’t accidentally lose administrative continuity.
