-
Processing status
Processes statuses pass on the status of single approval steps. You can set the processing status for each approval step in the approval workflow depending on whether the approval decision was negative or positive. Depending on the result of the approval decision, the appropriate processing status is set for the request.
For more information, see Processing status.
-
Standard reasons
Standard reasons are predefined reasons that can be selected in the Web Portal when making approval decisions.
For more information, see Standard reason for requests.
-
Approval policies
One Identity Manager uses approval policies to determine the approver for each request process.
For more information, see Approval policies for requests.
-
Approval workflows
Approval workflows define all the necessary steps for making approval decisions for request processes.
For more information, see Approval workflows for requests.
-
Approval procedure
Approval procedures are used to find the approvers required for an approval step.
For more information, see Setting up approval procedures.
-
Mail templates
Mail templates are used to send email messages to requesters and approvers.
For more information, see Custom mail templates for notifications.
-
Role classes
Use role classes to specify which company resources can be requested through the IT Shop. At the same time, you decide which company resources may be assigned as products to shelves and IT Shop templates.
For more information, see Role classes for the IT Shop.
-
Role types
Role types are used to group roles into a role class. Within the IT Shop, role types can e used to group shop and to restrict the effective approval policies for a shelf.
For more information, see Role types for the IT Shop.
-
Business Partners
In One Identity Manager, you can enter the data for external businesses that could be act as manufacturers, suppliers, or partners. You assign a manufacturer to a service item.
For more information, see Business partners.
-
Functional areas
To analyze rule checks for different areas of your company in the context of identity audit, you can set up functional areas. Functional areas can be assigned to service items.
For more information, see Functional areas.
-
Service categories
Service categories are used to group service items and make them available in the Web Portal.
For more information, see Entering service categories.
-
Tags
Product owners are able to add tags to their products. These tags can be used as search criteria by requests in the Web Portal.
For more information, see Entering tags.
-
Request properties group
When products are requested in the Web Portal, product-specific request properties can be queried dynamically. These request properties are displayed in the Web Portal depending on the configuration, requester, or approver. Request properties are saved as additional information in the shopping cart and in the request procedure.
For more information, see Entering product-specific properties.
-
Chief approval team
There is a default application role in One Identity Manager for the chief approval team. Assign employees to this application role, who are authorized to approve, deny, abort requests, or to authorize other approvers in special cases.
For more information, see Chief approval team.
-
Product owners
A default application role for product owners is available in One Identity Manager. Assign the employees to this application role, who are authorized to approve requests and edit the master data of service items or service categories.
For more information, see Product owners.
-
Attestors
A default application role for attestors is available in One Identity Manager. Assign the employees to this application role, who are authorized to attest IT Shop structures.
For more information, see Attestors.