Account Management v2

User access management (UAM) lets administrators control who can access an account and what they can do — whether you manage your own account or client accounts as a Channel Partner. Every account has its own users, roles, and environment configurations, so a well-designed access model ensures each team member has the permissions they need and nothing more.

Users, Use Cases, Roles, Permissions

User access management is built on a few related concepts:

graph TD
    U["User"]
    U --> UC["Use Case"]
    UC --> R["Role"]
    R --> E["Environment"]
    E --> SB["Sandbox"]
    E --> PR["Production"]
    R --> P["Permissions"]

1. A user is a person with a name, email, and optional phone number.
2. Each user is assigned to one or more use cases — the business scenarios (for example, KYC, fraud detection) the user works with.
3. For each use case, the user is assigned one or more roles. Roles can be system-defined (built into RiskOS™) or custom (created by your organization).
4. You can toggle each role independently for Sandbox and Production environments. A user can have broad access in Sandbox for testing and restricted access in Production.
5. Each role grants permissions across eight categories, each set to No Access, View Only, or Full Access.

Sandbox and Production environments

RiskOS™ maintains completely separate user and role configurations for Sandbox and Production:

Permission categories

Roles grant access through eight permission categories. You can set each category to one of three levels:

System Defined Roles

RiskOS™ provides system-defined roles as pre-built starting points for common permission sets. System-defined roles:

• Cover common access patterns out of the box.
• Cannot be edited or deleted.
• Cannot be inspected in an edit view — to understand what one grants, compare user behavior against the permission categories above.

Use system-defined roles as baselines before creating custom roles. For the full list of role types and how they appear in the Roles tab, see Roles & Permissions.

Custom Roles

When a system-defined role does not fit your needs, create a custom role with permissions tailored to a specific job function. Custom roles:

• Are created by your organization.
• Let you set each of the eight permission categories independently (No Access, View Only, or Full Access).
• Can be edited and deleted.

To create, edit, or delete a custom role, see Roles & Permissions.

Add and Manage Users

Add users to an account, then assign each one the use cases and roles they need — separately for Sandbox and Production.

• Add a user — enter the user's details, select their use cases, and assign roles per environment. See Manage Users.
• Edit or delete a user — update a user's details or roles, or remove their access. See Manage Users.
• Assign roles per environment — give a user different roles in Sandbox and Production. See Assign Roles.

In this section