Predefined roles reference
This page lists the seven system role templates that MapleGather seeds on every new organization, their default access areas, and the rules that apply to all system roles.
System role templates
Section titled “System role templates”| Role | Default access | Notes |
|---|---|---|
| Org Owner | Full access across all areas | Can invite and revoke admins, create custom roles, sign the DPA, manage subscription. The last remaining Org Owner cannot be revoked. |
| Finance Manager | Billing read/write, payments, refunds, subscription view | No access to member PII beyond what billing requires. |
| Communications Manager | Email send, segments, automations; read-only member list | Cannot edit member records. |
| Events Manager | Create, edit, and cancel events; manage check-ins | No access to billing or email. |
| Web Editor | Website CMS, page builder | No access to member records or billing. |
| Membership Manager | Membership levels, applications, renewals | No access to billing or email campaigns. |
| Read-only | View-only access across all areas | Safest starting role for new invites; grants no write permissions. |
Rules that apply to all system roles
Section titled “Rules that apply to all system roles”| Rule | Detail |
|---|---|
| Editable | No — system roles are read-only in the role editor. |
| Archivable | No — system roles cannot be archived or deleted. |
| Cloneable | Yes — clone any system role to use it as the starting point for a custom role. |
| Seeding | System roles are created automatically when a new organization is set up; you do not need to create them. |
| Multi-role | An admin can hold more than one role. Effective permissions equal the union of all held roles. |