Access And Plan Limits

Docs/Community & Discord/Access, permissions, and plan limits

Community & Discord

Access, permissions, and plan limits

Community & Discord requires Community & Discord or Everything.

Basic Discord connection may still be available to another paid workspace product when that product needs Discord for its own workflow, but that does not unlock Community & Discord analytics, Guard, onboarding, moderation, tickets, roles, or automations.

Workspace roles

Community & Discord uses the existing CollabOS workspace permission model.

Typical policy:

  • Owner and Admin manage setup and sensitive configuration
  • Lead can use selected operational features where permitted
  • Manager can use day-to-day operational or read features where permitted
  • Viewer remains read-only where supported

Discord permissions

Sensitive commands also respect Discord permissions and role hierarchy. Examples include:

  • Manage Server for many setup commands
  • Manage Channels for lockdown
  • Manage Roles for role assignment workflows
  • Moderate Members for warnings and moderation
  • View Audit Log for audit workflows

Subscription state

When Community & Discord is expired or inactive, product-gated Community & Discord features are locked until billing access is restored.

Custom bot name

Community & Discord and Everything can include the community-specific Brainer bot naming perk offered by CollabOS. If bot naming is not exposed as a self-service control in the current dashboard, it is handled as an account/server setup change rather than a Message Builder template.