Role-based access
Castlewatch roles determine which actions appear and which workflows are available. If a button or section is missing, role permissions should be checked before assuming the feature is unavailable. Organization policy thresholds can further restrict who manages members, partner requests, settings, and notification defaults.
Billing gates
Some operational areas require an active subscription before live use. This protects the workspace from partial production operation. If reporting, moderation, incident access, or organization administration appears locked, confirm the organization's billing state and plan status.
Billing checkout and billing portal flows intentionally navigate away from the current page because they depend on a hosted payment or account management flow.
Notifications
Notification behavior has two layers. Organization defaults define broad operating expectations. Personal alert preferences let each user control delivery per event, channel, severity threshold, quiet hours, and SMS destination when applicable.
- Use email for routine visibility and accountability.
- Reserve SMS for higher-signal events where immediate awareness matters.
- Set quiet hours carefully so urgent notifications still reach the right people.
Account settings
The account page manages profile details, sign-in posture, chat visibility, and personal notification preferences. Profile updates and alert preference changes happen on-page with visible success or error feedback. Password changes still require a fresh sign-in because active sessions are revoked.
Security posture
- Use recognizable display names and current email addresses.
- Enable authenticator MFA for administrators and reviewers where possible.
- Review role assignments after staffing changes.
- Disable accounts that should no longer have operational access.
- Keep chat visibility aligned with how the team uses internal coordination.