Looking for system permissions (like HR, Admin, Financial access)? See the Permissions Guide for controlling what users can do in the platform.
How to access
Settings → RolesUnderstanding Roles
Roles in Orgo serve two purposes:- Organizational Structure - Define positions like President, Secretary, Team Leader
- Permission Attachment - Optionally attach system permissions to roles
Examples of Organizational Roles
- President, Vice President, Secretary
- Team Leader, Project Manager
- Committee Chair, Board Member
- Regional Director, Local Coordinator
- Volunteer Coordinator, Membership Officer
Creating Roles
Set role scope
Choose where this role applies:
- National - Organization-wide role
- Local Center - Specific to a local center
- Parent Local Center - Regional (parent + children)
- Unit - Specific to a unit/team
Attach permissions (optional)
Select any system permissions this role should grant. See Permissions Guide.
Role Types
National Roles
Organization-wide positions visible across the entire organization. Examples: National President, Board Member, Secretary General Configuration: Enable “Is National” when creating the role.Local Center Roles
Positions within specific local centers/branches. Examples: Branch President, Local Treasurer, Membership Officer Configuration: Enable “Is Local Center” when creating the role.Parent Local Center Roles
Regional positions that span a parent center and its child centers. Examples: Regional Director, Area Coordinator Configuration: Enable “Is Local Center Parent” when creating the role.Unit Roles
Positions within specific units or teams. Examples: Team Leader, Project Manager, Committee Chair Configuration: Associate the role with a Unit Type.Role Properties
| Property | Description |
|---|---|
| Name | The role name (e.g., “President”) |
| Name Plural | Plural form (e.g., “Presidents”) |
| Position | Display order in lists |
| Chart Name | Name shown in organizational charts |
| Description | Explanation of role responsibilities |
| Permissions | System permissions attached to this role |
| Is National | Role applies organization-wide |
| Is Local Center | Role applies to local centers |
| Is Local Center Parent | Role applies to parent + child centers |
| Is User Type | Marks this as a membership category (see User Types) |
Assigning Roles to Users
Roles can be assigned through:Manual Assignment
Via Role Groups
Role Groups automatically assign roles based on criteria. Great for:- Adding “Active Volunteer” to users with 10+ hours
- Adding “Senior Member” to users with 5+ years membership
Via Import
Bulk assign roles during member imports. Learn more about Imports →Role Visibility Settings
Control who can see role information:| Setting | Description |
|---|---|
| USER | All members can see roles |
| HR_LOCAL | Only local HR and above |
| HR_TENANT | Only organization HR and above |
| ADMIN | Only administrators |
Roles with Permissions
When you attach permissions to a role, users with that role automatically receive those permissions. Example configuration:| Role | Attached Permissions | Result |
|---|---|---|
| Branch President | ADMIN_LOCAL | Full local center control |
| Regional Director | ADMIN_PARENT_LOCAL | Regional administration |
| Membership Officer | HR_LOCAL | Local member management |
| National Treasurer | FINANCIAL_TENANT | Organization-wide financial access |
See the Permissions Guide for detailed information about each permission level.
Best Practices
Match your organization structure
Match your organization structure
Create roles that reflect your actual organizational chart. This helps with reporting and communication.
Use meaningful names
Use meaningful names
Choose clear, descriptive names. “Membership Committee Chair” is better than “MC1”.
Document responsibilities
Document responsibilities
Use role descriptions to explain what each role is responsible for. This helps during transitions.
Set appropriate scope
Set appropriate scope
Use the correct scope level (national vs local vs unit) to keep roles organized.
Attach permissions thoughtfully
Attach permissions thoughtfully
Only attach permissions that every person in that role should have. Use separate permission assignment for exceptions.
Use role start/end dates
Use role start/end dates
When assigning roles, use dates to track terms. This helps with historical reporting.
Related Documentation
- Permissions - System permission levels and access control
- User Types - Membership categories (not position roles)
- Role Groups - Automatic role assignment
- Organizational Chart - Visualizing your structure