Qumuna roles and permissions explained
By Qumuna Editorial Team · Reviewed by Qumuna Product Review
Understand the difference between members, moderators, and administrators, assign granular moderator responsibilities, and keep elevated access within the community's plan and governance needs.
Short answer: Qumuna uses three community roles: member, moderator, and administrator. Administrators have broad community authority; moderators have baseline authority to review and act on moderation reports and can receive additional specific management permissions.
Three roles with different responsibilities
Members participate without management powers. Administrators are responsible for the full community. Moderators have baseline community-scoped moderation authority and can receive grants for selected additional areas such as members, handbook, files, or organizational units.
Granular moderator permissions
Moderation is a baseline moderator responsibility rather than an optional granular grant, but a moderator title is not a universal pass to every other management feature. The permissions checklist lets administrators match additional access to an actual responsibility, reducing the need to make every volunteer an administrator and making handover easier to explain.
Plan caps and governance boundaries
Elevated-role counts are limited by the community's current plan and enforced by the server, not merely by a disabled button. Communities should review elevated access regularly, remove grants that are no longer needed, and retain an urgent route outside the platform for safeguarding or account compromise.
Related resources
Next step
List each recurring leadership task, assign the least powerful role and grant that can complete it, and review the result with another administrator. Check current plan limits before appointing the team.
