Page Comparison

When users a user initiates a request for access to resources, they initiate workflows that attempt the corresponding EmpowerID workflow attempts to execute one or more EmpowerID Operations on those resources in a manner consistent with the workflow. For instance, if a user requests predefined operations on the target resources. For example, a user requesting membership in a Management Role , the associated workflow tries to perform operations on triggers a workflow that performs operations to update both the user and the Management Role to update the person's role membership. accordingly.

By default, if a user can initiate a workflow but lacks access to execute one or more operations within it, the authorization engine returns a message stating that the required access is missing. This default mode is suitable for admin workflows that do not the user has the privilege to initiate but not execute all operations within the workflow, the EmpowerID Authorization Engine returns a message indicating missing access rights. This default behavior is suitable for administrative workflows that don't require approval. For processes that need needing approval, EmpowerID offers a robust workflow engine that can be enabled on a per-workflow basis.

Workflow Approval Routing

Organizations can override the default approval process for greater control over how the system generates and manages approvals. Each workflow has a property called EmpowerID allows organizations to override default behavior through its robust Workflow Approval Engine, which is configurable on a per-workflow basis. Each workflow includes a property known as "Do not generate a business request (no approval)," which is enabled by default for most workflows by default.

The approval process logic, in relation to the "Do not generate a business request (no approval)" property on a given workflow, occurs as follows:

1. True state: EmpowerID checks if the person executing the workflow initiating user possesses the necessary RBAC access to carry out the Role-Based Access Control (RBAC) rights needed for all operations within the workflow. If the person does have access is sufficient, the workflow proceeds; if not, EmpowerID informs the person user of their access insufficiency, and the workflow is terminatedterminates. No approval routing happens in this case. This method reduces the number of approval tasks generated and removes unnecessary actions from the approval process.

2. False state: In this case, the workflow must be The workflow is associated with a specific Business Request Type and will always require necessitate approval, even if the individual has the authority to execute the workflow operationsirrespective of the user's RBAC permissions. The Business Request Type property categorizes workflows, enabling more flexible approval routing and grouping related access requests. This property, coupled with new used in conjunction with EmpowerID’s Approval Flow and Access Request and Approval Flow policies, permits organizations to consolidate related allows the aggregation of similar access requests into a single "approval bundle," specifying who should receive approval tasks and determining the number of approvals needed before fulfillment.
   

Image Removed

Image Added

Approval Flow Policies: Structuring Approvals

EmpowerID’s Approval Flow policies guide the approval routing of access requests, known as "Business Requests," which users submit via the IAM Shop.

When users shop for resources in the IAM Shop and submit their orders, these items are sent as "Business Requests" to the EmpowerID system. These requests are routed for approval based on Approval Flow policies, which can be adjusted to create multi-tiered approval processes based on the organization's requirements.

Key components of Approval Flow policies that can be configured include:

1. Business Request Type: A workflow property that groups workflows by the type of business request they represent, like the IT Shop Business Request Type. Approval Flow policies can stipulate multiple levels of approval for certain Business Request Types before fulfillment. Approval flow at the Business Request level is sometimes referred to as global-level approval flow.

2. Approval Flow Steps: Define the number of approvals required for fulfillment, with each step representing a sequential stage that must be approved before progressing. Each step can be optionally configured for "step-level" fulfillment. This means that a step can run a workflow and perform some action based on the decision made at that step. Step-level fulfillment is often used to execute an action when the approver's decision results in a rejection, stopping the forward processing of the approval flow. The normal fulfillment process for an item request only executes if all steps are approved.

3. Item Level Approval: Each step can allow Item Level approval, enabling the approver to make decisions on each item instead of a single decision for the entire Business Request.

4. Approver Resolver Rules: Dictate who the Approval Flow Step should route for approval. These can be routed to various actors in EmpowerID to include the:

   • Initiator Manager – The request routes to the manager of the person initiating the request

   • Target Person Manager – If making a request for another person, the request routes to that person’s manager for approval

   • Resource Owner – Owner of the item resource

   • Global Resource Owner – Owner of the resource specified as the subject of the Business Request. This allows items to be routed for approval to the subject of the request such as the group instead of to each account being added as a member.

   • RBAC Approver – Anyone with the RBAC delegations needed to approve the request

   • Static Approver – Approvers are specific users selected for the step

   • Fallback Approver – Can select someone to approve in the instance that a specified approver does not exist, such as would be the case if a Management Role was selected as a Static Approver and no one had that role

5. Items Types and Item Type Actions: Item Types are the individual resources that can be requested, and Item Type Actions represent actions that can occur against an item. Examples of Item Type Actions include Add Account To Group or Assign Azure License.

Multi-level Approval Flow Logic

EmpowerID 's approval flow, despite the multiple components, follows a straightforward logic. Items have two opportunities to be approved: at the allows for two levels of approval: Business Request level and Item level. Rejection at the individual item level. If a Business Request is rejected at any step in this approval flow, the process endsBusiness Request level (the global level) terminates the entire process. Only items approved at the Business Request Level progress to the next step, where they can optionally be approved at the individual item level.

Business Request Level

At this level, the Approval engine looks at the Business Request Type to see if the type is defined with any Approval Flow policies per Access Request policy. If the Business Request Type is not defined as specified, nor defined for the Access Request policy of the target resource for the type, then the engine checks the Business Request itself to determine the Approval Flow policy.

Item Level

At this level, the Approval engine first checks the Item Type Action per the Access Request policy to see if the policy designates different Approval Flow policies for the item based on its Access Request policy. If there isn't a specific Access Request policy defined for the Item Type Action, the engine checks the Item Type Action itself for a specific Approval Flow Rule. If there isn't a specific Approval Flow Rule set, the Approval engine falls back on the Approval Flow Policy for the item as specified on the item's Access Request policy. 

Image Removed

Image Added

Figure 4 3 above illustrates how approval flows work in EmpowerID at a high level. This example creates a new Business Request to onboard an employee. The onboarding request includes a Business Role, an A"” , a group, and a Management Role. Once all levels of approval are cleared, items in a Business Request can proceed to fulfillment. This process is managed by the Business Request Item Fulfillment Job, which handles items ready for fulfillment in two ways, based on whether they are associated with Correlation IDs.

1. Fulfill in Different Workflow (No Correlation ID): Items without Correlation IDs are directed to the fulfillment workflow specified for their related Item Action Types. For instance, if a user is to join a Management Role, the designated workflow for that action would fulfill the item. These items never return to the initial workflow operation for resumption; instead, the calling workflow exits the process.

2. Fulfill in Initial Workflow (Correlation ID): Items bearing Correlation IDs are routed back to the originating workflow operation, where approval was a prerequisite to proceed.

The fulfillment process, according to the existence of Correlation IDs, is depicted in Figure 54.

Notification Policies

As part of the approval process, EmpowerID sends notifications to request approvers, initiators, and delegated users as part of the approval process. The approval process allows users to customize the frequency and type of notifications they receive. Here's how notifications function in EmpowerID:

1. A Business Request Event is created each time a user submits a Business Request.

2. Business Request Events are submitted to the Business Request Notification Policy engine.

3. The engine determines if the event needs to be added to the Business Request Notification Inbox by first examining individual users' notification preferences and defaulting to system notifications if no personalized settings exist.

4. Notifications are then sent to Business Request participants based on these settings.

Notification Policy Components

Several components drive the Notification policies and how the Notification Policy engine delivers notifications. These include:

• Business Request Events: Four levels of events where notifications can be triggered: Created, Open, Approver Set, Fulfillment Ready, and Fulfillment Completed, and Completed.

• Business Request Participant Type: Individuals associated with a specific part of a business request. These can include the Initiator, TargetPerson, InitiatorManager, TargetPersonManager, Approver, Approver Manager, Potential Approver, and Commenter.

• Levels: Several levels can be designated for notifications, including Business Request, Business Request Item, Business Request Approval Step, and Business Request Item Approval Step.

• Messages: Email messages delivered by the notification engine to Business Request participants.

Business Request Expiration

Setting expiration dates for business requests is important for the efficient management of the requests. It ensures that approvals are completed within specific timelines, helping organizations meet regulatory requirements. Once the business requests are expired, it doesn't appear for any approvers, thus managing the requests better. EmpowerID has two strategies based on expiration dates for handling business request expiration.

The first is a fixed 90-day policy, based on an expiration date, which automatically expires any incomplete requests after 90 days. The second strategy is more dynamic based on the inactivity expiration date, calculating the period of inactivity based on user actions. The types of expirations date in EmpowerID are

Expiration Date - When a business request is created, it is assigned an expiration date in the "ExpirationDate” field. If a specific number of days is explicitly provided for the process, that will be used. Otherwise, the default expiration date will be set to 90 days from the creation date.

Inactivity Expiration Date - The inactivity expiration date is different from the previously discussed expiration date. It is dynamic and varies based on the user's activity on the generated business requests. The calculation of this date involves adding the number of days specified in the "ExpireRequestAfterXDaysOfInactivity" field of the Business Request Type to the current date. Whenever someone interacts with the process, such as approving, rejecting, setting a new approver, triggering an escalation, etc., the inactivity expiration date shifts X days into the future. Therefore, every time there is an activity in a business request, the inactivity expiration date gets recalculated by adding the days specified in the business request type of the business request item.

The job “Business Request JSON Inbox Processor“ is responsible for finding expired business requests and setting their status as expired. For a business request to be considered "expired," it must meet two conditions:

• Status: The request should be in an "Open" or "In Progress" status, indicating that it is still active and has not been completed or canceled.

• Expiration Dates: Either the expiration date or the inactivity expiration date mentioned earlier is passed.

So, if the "Business Request JSON Inbox Processor" finds a business request that meets these two conditions, it will update the status of that request to "Expired." Consequently, the expired request will no longer show up on the list of tasks for approval by any approver, ensuring that no further actions are taken on a request that is no longer valid.

Approval Flow Demo

The following video demonstrates how to configure approvals and approval routing in EmpowerID.