Roles and Privileges

A brief explainer about the various roles and permissions in Breach Commander

As started in our previous article Breach Commander roles : Who's behind the keyboard, our solution allows to customize the data access and user experience according to what you want them to access. You may want to read it first.

Flexible roles and privileges give a custom journey to each User

What are the roles and privileges?

Roles

Roles are operational assignments that allow a User to:

• Access the Cases to which they are assigned; and

• Answer the workflow steps of their Cases.

Breach Commander roles are:

The user roles in Breach Commander

• Incident Commander :

• Business Lead

• Technical Lead

• Audit Lead

The user editing section gives the administrators of each Tenant (with user editing privilege) the possibility to define which roles a User can bear. A User can have multiple roles assigned within a Tenant, and simultaneously play multiple roles within a Case.

When a User holds a role, they obviously appear in the assignment section if the Case creation/edition section.

Only the users with the proper role can answer to the steps in the Case they are assigned to.

Privileges

Privileges define which data or configuration objects a User can access.

The "power" levels are:

• None (No access)

• Read

• Change

The available permission scopes are:

• Tenant

• Organizations

• Users

• Cases

• Audits

• Application Programming Interface (API)

Breach Commander has granular controls so that each user has access to everything they need to do their work, and only access what you allow them.

Visit breachcommander.com and join the conversation about roles !