Platform
Roles that mean what they say
Four roles out of the box, built from named capabilities so you can shape your own. Enforced at the API, not just hidden in the menu.
Platform Super AdminThe operator. Usually Beakforce; can be your technical staff.
- Configure branding, modules, language and region
- Configure integrations and registration policy
- Manage administrative roles
- View platform health, usage and billing metrics
Community AdminYour team. Runs the community day to day.
- Manage members, groups, forums, events and content
- Appoint moderators and manage guidelines
- Review reports and configure categories
- Cannot enable unlicensed modules, touch infrastructure, grant Super Admin or change billing
ModeratorOperational. Keeps things civil.
- Review the report queue
- Remove content (quarantine), issue warnings and strikes
- Suspend members within the policy you set
- Cannot configure the platform
MemberEveryone else.
- Participate in every enabled module
- Own their profile and privacy settings
- Report content, appeal decisions
- Earn trust that unlocks more
Capabilities, not checkboxes
Under the hood a role is a set of named capabilities: community.manage, events.manage, moderation.review, moderation.sanction and so on. That's what lets you create an Event Manager who can run the calendar and nothing else, or a Community Manager who runs groups and forums but never sees the moderation queue.
Custom rolesCompose from existing capabilities without waiting for a release.
Group leadersDelegated authority inside one group, invisible outside it.
Trust levelsMembers unlock posting, DMs or marketplace access by earned trust, separately from any role.
Tested boundariesAutomated tests prove a moderator can't configure the platform and a community admin can't grant Super Admin. On the API, not the UI.
