Privileges: Overview

Summary: High-level overview of the privileges available to roles in RiskSense's Identity and Access Management (IAM).

Role-based access control is designed where privileges determine what a person can do within the platform. Roles are comprised of a set of privileges. You then assign users one or more roles based on their job and scope of work. This system allows you to define what users can and cannot do within the limitations of the system (in this case, RiskSense).

Each privilege carries one or more allowances:

Allowed is the explicit granting of a privilege. If any one role is set to allow, the user has access to that feature or function.

Not Allowed explicitly denies access to that privilege. If any role for a user is not allowed, the user cannot make use of that feature or function. If the user is assigned multiple roles which contain both allowed and not allowed statuses for a specific privilege, the not allowed status is honored.

Enforced is a superset of both allowed and not allowed, denoting that a privilege status is explicitly affected by a given role.

Not Enforced is the other side to the enforced coin, neither allowing nor denying the privilege. If no roles granted to a user allow the privilege, it is considered an implicit denial of that privilege.

The rest of this article provides all privilege and privilege descriptions available in RiskSense’s Identity and Access Management (IAM).