Identity Governance & Administration
sara.next
  1. sara.next
  2. Platform
  3. Roles and policies

Platform · Access management

Roles and policies

Access is not just "a role in an application". Who approves it and who later verifies it is decided by its scope: company, country, department, project.

Model

What a single access entry consists of

WhoTo whatIn what scopeWho decidesUsere-mail or loginApplicationcategory · flagsRolerequest typesAttributescompany · country · departmentDictionariesallowed valuesApproverderived from rulesReviewerderived from rulesAccess recorduser + role + scope

Expert view

A role is not enough — scope is what counts

A model based solely on roles looks good on a slide and scales badly in practice. If "company A accountant" and "company B accountant" are separate roles, an organisation with thirty companies and ten roles has three hundred roles to maintain. After a year nobody knows how they differ.

sara.next separates these two things. The role says what the user can do. The attributes — company, country, department, project — say in what scope. There are few roles, and the scope is chosen in the request from dictionary-based lists. The same attributes are then used to determine the approver and the reviewer.

Policies, or what the system will not let through

A rule such as "only one person may hold this role in a given country" written in a procedure will be broken one day. Written as a limit in the role configuration, it will not, because the request simply cannot be submitted. The same applies to validators and conditional fields: a rule enforced by the system does not need to be remembered.

Practical advice: dictionaries are the foundation. If the list of departments in the system does not match the actual structure, no rule will work correctly. It is worth synchronising them from the source that owns them instead of maintaining them manually.

Elements of the model

Four levels of configuration

Application

What is under control

Name, category, how the user is identified, participation in reviews.

Role

What access

Allowed request types, review actions, a description visible to the user.

Attribute

In what scope

A list, multiple choice or a value computed automatically.

Dictionary

From which values

Reference data: imported from files or synchronised from sources.

Policies

Rules enforced by the system

Limit of people in a role

The maximum number of users in a role in a given context, e.g. in a country. When it is exceeded, the system suggests changing the user.

Validators

Conditions that must be met to file a request for a role at all.

Conditional attributes

Fields that are required, hidden or recalculated depending on other choices.

Exclusions

Dictionaries of allowed and excluded values for an attribute.

Read-only mode

A role visible in the catalogue but not available for requests.

Decision-maker rules

Approvers and reviewers follow from the role and the request attributes.

See sara.next on your own scenarios

During the presentation we will walk through an access request, approval, automatic execution of the change and a review — using examples from your organisation.