What are roles and why do we need them?
User roles control what each person can see and do. Instead of giving everyone the same type of account, roles let you assign different levels of access — so people have just the tools they need, and nothing more. This is particularly relevant in the management area, which is why there are different roles with various permissions. We recently redefined the roles to further increase security and flexibility.
⚠️ What changed?
RideAmigos now uses three clearly defined roles — Admin, Manager, and Program Coordinator — to make access control easier and more secure in the management dashboard.
- Admins have full instance-wide control
- Managers have full network control (but only for assigned networks)
- Program Coordinators can edit programs only (in assigned networks)
The RideAmigos team always has top-level access to help with additional changes.
Old Roles vs New Roles
| Old Role | New Role |
| Network Manager | Program Coordinator |
| Advanced Network Manager | Manager |
| System Admin | Admin |
New Role Definitions
Admin (Full Instance Access)
- Access to all networks and settings
- Full control over users, networks, programs, and configuration
- Equivalent to old System Admin
Manager (Network-Level Access)
- Full control over a specific network and its subnetworks
- Manage users, networks, programs at that level
- Equivalent to old Advanced Network Manager
Program Coordinator (Program Access Only)
- Can edit programs and rewards
- Cannot view or manage users/networks
- Equivalent to old Network Manager
Permission Matrix
| Feature / Tool | Program Coordinator | Manager | Admin |
| Explore Options Setup | ❌No Access | ✅ Full Access | ✅ Full Access |
| Triplog Setup | ❌No Access | ✅ Full Access | ✅ Full Access |
| Users | ❌No Access | ✅ Full Access | ✅ Full Access |
| Networks | ❌No Access | ✅ Full Access | ✅ Full Access |
| Programs / Rewards | ✅ Full Access | ✅ Full Access | ✅ Full Access |
| Challenges | ✅ Full Access | ✅ Full Access | ✅ Full Access |
| Send Emails | ❌No Access | ✅ Full Access | ✅ Full Access |
| Reports | ✅ Full Access | ✅ Full Access | ✅ Full Access |
| Journey Builder | ❌No Access | ✅ Full Access | ✅ Full Access |
| Appearance / Configuration | ❌No Access | ❌No Access | ✅ Full Access |
| Mobile App Settings | ❌No Access | ❌No Access | ✅Full Access |
| Proxy as User | ❌No Access | ✅ Full Access | ✅Full Access |
| Manage Permissions | ❌No Access | ❌No Access | ✅Full Access |
Example Scenarios
- Regional lead: Program Coordinator for Region A
- Corporate mobility manager: Manager for Network B
- Site owner / top-level admin: Admin for the entire instance
Users can hold different roles in different networks.
Example: Alex is a Manager in Network A, but just a User in Network B.
Who should get which role?
-
Admin (instance-wide access)
For top-level system owners who need to control all settings, users, networks and access to their data. They have extensive full access and should only be selected individuals within an organization.
-
Manager (network-level access)
For leaders who manage users, programs, and subnetworks within a specific network. For example, they can manage a department's network without being able to change the entire setup and branding of the organization.
-
Program Coordinator (program-only access)
For staff who just need to edit and manage programs or incentives, but don’t need user or network access. For example, they can run programs without seeing the addresses of the people participating.
☝️If your platform is part of a regional connected ridematching system your permissions may differ. Get in touch with your customer success manager or submit a support request if you have questions.