Identity Governance & Administration
sara.next
  1. sara.next
  2. Resources
  3. Application onboarding

Knowledge base · For administrators

Application onboarding

Application onboarding means turning what was agreed with the application owner into configuration: what the roles are, what determines the access scope, who approves and who later verifies. Everything is done in the administration panel.

  • for administrators
  • approx. 12 minutes

Order

What depends on what

DataModelProcessDictionariescompanies · countries · departmentsAttributeslinked to dictionariesApplicationcategory · flagsRoles8-step configuratorDecision-makersrule blocksRequest processworkflowAccess importinitial state

Step 1

Dictionaries and attributes

Start with the reference data. A dictionary is a list of values with codes — e.g. companies, countries, departments — that the user will choose in the request. You add it manually or import it from a file in the configuration tab.

Next you create attributes (called dimensions in the panel) and link each one to a dictionary. An attribute without a dictionary has no use. For each attribute you choose how it is presented in the request:

  • list — choosing a single value,
  • multiple choice — several values at once,
  • computed value — set automatically based on other data.

TipThe system name of a dictionary, attribute, application and role is assigned once and cannot be changed later. The display name can.

Step 2

The application and its settings

In the application editor you enter the name, category and how the user is identified, and then enable the options you need.

The application and its settings
SettingMeaning
CategoryGroups applications on the list when filing a request and when searching.
User identification attributeHow the application recognises the user; the same key then applies when importing access.
ActiveSwitching it off hides the application but does not delete it.
SOXThe application takes part in the periodic review and appears in the SOX application report.
Requests enabledUsers can file access requests.
Bulk approvalThe approver can decide on many requests at once.
Automatic approval notificationAn e-mail every time automatic approval is applied.
User data change notificationAn e-mail to the application manager when a user's attributes change.
Expiry dateThe user can set an access deadline in the request.

Step 3

Role: the eight-step configurator

The role is the heart of the configuration. Once the name is saved, the further steps are unlocked.

  1. Role name

    The system name, the display name and a description shown to the user when choosing the role.

  2. Request and review types

    Which operations are allowed: grant, modification, change of user, removal — separately for requests and reviews.

  3. Role attributes

    Which attributes define the scope; for each: required, conditionally hidden, dictionary of values and exclusions.

  4. Access validation

    A limit on people in the role in a given context, a custom message and additional validators.

  5. Approver

    A rule block that derives the approver, or pointing to a specific role.

  6. Second approver

    An optional second level of approval.

  7. Reviewers

    Who verifies the access in the periodic review — configured in the same way as approvers.

  8. Request process

    Choosing the workflow and its additional properties.

Good to know

Role options that save work

  • The author can withdraw the request — until the main approval.
  • Read-only mode — the role is visible but cannot be requested.
  • Hiding the start date — when access always starts immediately.
  • Additional information step — the implementer can ask a designated person for details before granting access.

Limit of people in a role

A threshold of "0" means no limit, "1" means that only one person can hold the role in a given context (e.g. a country). It is a simple way to enforce the principle of a single responsible person and prevent excessive assignment of broad-scope roles.

Change control

When saving the configuration, the panel asks for a ticket number from the ticketing system. Once you enter it, a bar with the number appears at the top of the screen, and all further changes in that session are assigned to it.

Step 4

Importing existing access

Finally you load the list of people who already have access to the application. The import works with .xlsx files: you select the application, the file, the user identification key (e-mail address or directory login) and map the columns to the user, role, expiry date and attributes.

Before saving, the system shows a summary: how many rows are valid and how many are invalid, with a result file to download. Only then do you confirm or cancel the import. The import does not trigger approval — instead it requires naming the application manager or business owner as the approver and entering a justification.

NoteThe data must be on the first sheet of the file, and the role names and attribute values must match the dictionaries in sara.next.

Planning to bring more applications under control?

We will help gather requirements from application owners and prepare the configuration.