Members
The Members page provides Administrators with a centralized view of all users within the tenant. From here you can manage user accounts, assign application-level roles, and control access.
Required role: Administrator or SuperUser
Accessing the Members Page
Section titled “Accessing the Members Page”Navigate to Administration > RAMP Tenant Members (or /_admin/ramp-tenant-members).
The members list shows all users in the current tenant, including:
- User display name and email
- Active or inactive status
- Assigned application roles
- Authentication method (RAMP Internal, LDAP, OIDC, Windows Auth)
Creating a User
Section titled “Creating a User”For tenants with RAMP Internal authentication enabled, Administrators can create user accounts directly.
- Click Create User on the members page.
- Fill in the required fields:
- Username — must be unique within the tenant
- Email — the user’s email address
- First Name and Last Name
- Password — set an initial password
- Click Create.
Editing a User
Section titled “Editing a User”- Click on the user in the members list.
- Modify profile information (display name, email, etc.).
- Click Save.
Assigning Application Roles
Section titled “Assigning Application Roles”Application-level roles (App Roles) determine what a user can do across the entire RAMP tenant. These are separate from entity-specific roles (template roles, instance roles) that are assigned on individual items.
- Click on the user in the members list.
- Open the Roles tab.
- Click Add Role.
- Select the desired role from the dropdown.
- Click Assign.
Available Application Roles
Section titled “Available Application Roles”| Role | Purpose |
|---|---|
| Administrator | Manage system settings, users, groups, and configuration. Cannot access content without additional roles. |
| SuperUser | Full access to all templates, instances, and systems. Use sparingly. |
| TemplateCreator | Can create new templates. Automatically becomes Template Owner on created templates. |
| GlobalTemplateOwner | Owner permissions on all templates system-wide. |
| GlobalTemplateEditor | Editor permissions on all templates system-wide. |
| GlobalTemplateViewer | Read-only access to all templates system-wide. |
| GlobalTemplateApprover | Can approve versions on all templates system-wide. |
| GlobalInstanceHead | Head permissions on all instances system-wide. |
| GlobalInstanceDeputyHead | Deputy Head permissions on all instances system-wide. |
| GlobalInstanceEditor | Editor permissions on all instances system-wide. |
| GlobalInstanceExecutor | Executor permissions on all instances system-wide. |
| GlobalInstanceObserver | Read-only access to all instances system-wide. |
| SystemManager | Can manage systems and stages. |
| CalendarManager | Can manage calendars and scheduling. |
| MessageSubscriber | Receives general system notifications. |
| PreEscalationSubscriber | Receives pre-escalation warnings. |
| EscalationSubscriber | Receives escalation alerts. |
For a comprehensive explanation of each role and its permissions, see Roles.
Removing Roles
Section titled “Removing Roles”- Navigate to the user’s Roles tab.
- Click the remove button next to the role you want to revoke.
- Confirm the removal.
Deactivating a User
Section titled “Deactivating a User”To prevent a user from logging in without deleting their account:
- Click on the user in the members list.
- Toggle the user’s status to Inactive.
- Click Save.
Deactivated users cannot log in but their data and role assignments are preserved. You can reactivate the account at any time.
Resetting a User’s Password
Section titled “Resetting a User’s Password”For RAMP Internal users, Administrators can reset passwords:
- Click on the user in the members list.
- Click Reset Password.
- Set a new password.
- Communicate the new password to the user through a secure channel.
Best Practices
Section titled “Best Practices”- Principle of least privilege — assign only the roles a user needs for their work. Start with lower-privilege roles and escalate as needed.
- Use groups for bulk role assignment — instead of assigning the same role to many individual users, create a group and assign the role to the group.
- Regular audits — review role assignments periodically. Remove roles from users who have left or changed positions.
- Multiple administrators — ensure at least two users have the Administrator role to avoid lockout scenarios.