Chat now with support
Chat mit Support

Identity Manager 9.3 - IT Shop Administration Guide

Setting up an IT Shop solution
One Identity Manager users in the IT Shop Implementing the IT Shop Using the IT Shop with the Application Governance Module Requestable products Preparing products for requesting Assigning and removing products Preparing the IT Shop for multi-factor authentication Assignment requests Delegations Creating IT Shop requests from existing user accounts, assignments, and role memberships Adding system entitlements automatically to the IT Shop Deleting unused application roles for product owners
Approval processes for IT Shop requests
Approval policies for requests Approval workflows for requests Determining effective approval policies Selecting responsible approvers Request risk analysis Testing requests for rule compliance Approving requests from an approver Automatically approving requests Approval by peer group analysis Approval recommendations for requests Gathering further information about a request Appointing other approvers Escalating an approval step Approvers cannot be established Automatic approval on timeout Halting a request on timeout Approval by the chief approval team Approving requests with terms of use Using default approval processes
Request sequence
The request overview Requesting products more than once Requests with limited validity period Relocating a customer or product to another shop Changing approval workflows of pending requests Requests for employees Requesting change of manager for an employee Canceling requests Unsubscribe products Notifications in the request process Approval by mail Adaptive cards approval Requests with limited validity period for changed role memberships Requests from permanently deactivated identities Deleting request procedures and deputizations
Managing an IT Shop
IT Shop base data Setting up IT Shop structures Setting up a customer node Deleting IT Shop structures Restructuring the IT Shop Templates for automatically filling the IT Shop Custom mail templates for notifications Product bundles Recommendations and tips for transporting IT Shop components with the Database Transporter
Troubleshooting errors in the IT Shop Configuration parameters for the IT Shop Request statuses Examples of request results Example of defining request properties

Determining approvers via approval roles

The DI, DR, ID, IL, IO, IP, PI, PR, RD, RL, RO, RP approval procedures are used to determine the approvers through the application roles for role approvers and role approvers (IT). These application roles can to assigned to hierarchical roles (departments, locations, cost centers, business roles). If no application role is assigned to the hierarchical role or this application role has no members, the approvers are determined according to the following principle.

Example: Determine the approvers using the RD approval procedure (Role approvers of the recipient's primary department)

  1. This determines the request recipient's primary department (UID_Department).

  2. The application role (UID_AERole) is determined through the department’s role approver (UID_RulerContainer).

  3. Determine the secondary identities assigned to this application role. These can issue approval.

  4. If there is no approver given for the primary department or the application role has no members, the approver of the parent department is used.

  5. If no approver with members can be determined right up to the top department, the request cannot be decided.

NOTE: When approvers are determined using the approval procedures RO or IO, and inheritance for business roles is defined from the bottom up, the following applies:

If no role approver is given for the primary business role, the role approver is determined from the child business role.

Related topics

Determining target system managers as approvers

Every target system connected to a One Identity Manager, can be assigned target system managers. These target system managers can be determined as approvers for requesting system entitlements.

Related topics

Determining requester or recipients

Requesters or recipients of requests sometimes become involved in the approval process. For example, they may have to answer inquiries. The following approval procedures determine the requesters or recipients as approvers.

Related topics

Determining special identities as approvers

Requesters can enter an identity as approver directly into the request. For example, this can be used to assign a manager to the request recipient. This new manager can approve or deny the assignment.

Related topics
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen