Understanding User Roles in the RHL ASM Platform
The RHL ASM Platform supports multiple user roles to help organizations manage access and permissions based on responsibilities and use cases. Each role has specific privileges and scopes of access, particularly in relation to organization settings and Asset Groups.
Below is a breakdown of the available user roles:
Admin
- Has full access to the entire platform.
- Can manage:
- All Asset Groups
- Integrations
- Notification Preferences
- Organization Settings
- Intended for platform owners and core security administrators.
User
- Has access to all Asset Groups.
- Cannot modify organization-wide settings or manage integrations.
- Suitable for internal team members who need visibility and limited control.
Restricted User
- Has read-only access to all Asset Groups.
- Cannot modify data or change any settings.
- Ideal for stakeholders or analysts who require full visibility without edit permissions.
Vendor
- Has read-only access to a specific Asset Group only.
- Cannot access or view other Asset Groups.
- Designed for external partners, contractors, or third-party vendors.
Subsidiary
- Has read-only access to a specific Asset Group only.
- Similar to Vendor in permission level.
- Best suited for sub-entities within the organization, such as subsidiaries or regional teams.
Summary Table
| Role | Org Settings Access | Access Scope | Permissions |
|---|---|---|---|
| Admin | Yes | All Asset Groups | Full Access |
| User | No | All Asset Groups | Limited Edit |
| Restricted User | No | All Asset Groups | Read-Only |
| Vendor | No | Specific Asset Group | Read-Only |
| Subsidiary | No | Specific Asset Group | Read-Only |
Assigning appropriate roles ensures secure and structured access across your organization.