User Roles¶
[Draft — pending review]
A role defines what a user can see and do in Ordinate. Every user is assigned exactly one role, which controls:
- Feature access — which features and sub-features they can use, and to what level (view, edit, delete, administer, etc.)
- Location visibility — which meeting locations and zones they can see
- Restricted people access — whether they can view people marked as restricted
Roles are custom-defined by your organisation — you can create as many roles as needed to match your team structure. Common examples include Administrator, Coordinator, Receptionist, and Read-Only User.
Managing Roles¶
Roles are managed from the role management interface. For each role, you can configure:
- Name — a descriptive name for the role
- Location group access — visibility of all location groups, or only selected ones
- Restricted people — whether this role can see people flagged as restricted
- Feature permissions — the detailed permission matrix (see Features and Permissions)
Creating and Deleting Roles¶
- New roles can be created from scratch, or by cloning an existing role. Cloning is useful when a new role is similar to an existing one but needs a few adjustments.
- Deleting a role is only possible if no users are currently assigned to it (either as their default role or as an event-specific override). You will need to reassign any affected users to a different role before deleting.
Per-Event Role Overrides¶
A user's default role applies across all events, but you can assign a different role for specific events. For example, someone who is usually a standard user might need administrator access for an event they are helping to organise. See Customise User Roles Per Event.