Chat now with support
Chat with Support

Identity Manager On Demand - Starling Edition Hosted - 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

Specifying dependencies between products

You can define dependencies for products. For example, when a printer is requested, a flat-rate installation charge has to be requested at the same time, and toner may be requested optionally. You can also specify if two products should never be requested simultaneously.

Dependencies between requestable products are created using service items.

When a product is requested, it is tested for dependencies and in this case, dependent products are added to the request.

To specify dependencies between products

  1. In the Manager, select the IT Shop > Service catalog > Hierarchical by service categories > <service category> category.

    - OR -

    In the Manager, select the IT Shop > Service catalog > Hierarchical by service categories > Singles category.

  2. Select the product's service item in the result list.

  3. Select the Edit product dependencies for requests task.

    • In the Dependent products tab, specify the dependent products.

      In the Add assignments pane, assign the service items.

    • In the Depends on products tab, specify which selected service item is dependent on which products.

      In the Add assignments pane, assign the service items.

  4. Save the changes.

  5. Select the Service item overview task.

  6. Define the properties of the product dependency.

    1. On the Dependent products or Depends on products form element, select the dependent product.

      This opens the product dependency details form.

    2. Specify the dependency conditions. Select one of the following options:

      • Cannot request products together

        This option prevents the dependent product from being acquired by the same request. The product can be assigned at any time with a separate, direct request.

      • Product must be requested at the same time

      • Product can optionally be requested with another

  7. Save the changes.

Editing product dependencies for requests

Dependencies between products are taken into account by Web Portal requests.

Detailed information about this topic

Defining hierarchy for service items

You can structure service items hierarchically. To do this, assign a service item below or above another service item.

To structure service items hierarchically

  1. In the Manager, select the IT Shop > Service catalog > Hierarchical by service categories > <service category> category.

    - OR -

    In the Manager, select the IT Shop > Service catalog > Hierarchical by service categories > Singles category.

  2. In the result list, select a service item in the result list and run the task Edit service item hierarchy.

  3. Select the Child service items tab.

    In the Add assignments pane, assign child service items.

    TIP: In the Remove assignments pane, you can remove service item assignments.

    To remove an assignment

    • Select the service item and double-click .

  4. Select the Parent service items tab.

    In the Add assignments pane, assign parent service items.

    TIP: In the Remove assignments pane, you can remove service item assignments.

    To remove an assignment

    • Select the service item and double-click .

  5. Save the changes.

Assigning hierarchical roles to service items

You can use One Identity Manager to assess the risk of assignments. The assessments can be evaluated separately by role. Prerequisite is that service items are assigned to the roles. For more information about risk assessment, see the One Identity Manager Risk Assessment Administration Guide.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating