If you want an application to be available for requesting access (self or other), which of the following should be configured?

If you want an application to be available for requesting access (self or other), which of the following should be configured?
A . Proposed Accounts Workflow
B . Access Remove Workflow
C . Access Add Workflow
D . Emergency Access ID Request Workflow

Answer: C

Explanation:

To make an application available for access requests (either self-service or requests for others), the Access Add Workflow needs to be configured within Saviynt. This workflow defines the process that governs how access to the application is granted. Here’s a breakdown with Saviynt IGA references: Saviynt’s Access Request System (ARS): This is the module within Saviynt that handles access requests. The ARS relies on defined workflows to manage the approval and provisioning process. Access Add Workflow: This specific type of workflow within Saviynt’s ARS is triggered when a user requests access to an application or entitlement. It dictates the steps involved, such as: Requester Details: Capturing information about who is requesting access.

Application/Entitlement Selection: The user selects the application (and potentially specific roles or entitlements within that application) for which they are requesting access.

Approval Routing: Defining the approval chain (e.g., manager approval, application owner approval, etc.). This is configured within the workflow using various approval activities.

Provisioning: Upon approval, the workflow can trigger automated provisioning of access to the target system (if connected integration is set up).

Saviynt’s Application Onboarding: For an application to be available in the ARS, it needs to be onboarded into Saviynt. During this process, you would typically define the relevant entitlements (access rights) associated with the application.

Workflow Configuration in Saviynt: Saviynt’s admin interface allows administrators to create and customize workflows using a visual designer. This includes setting up conditions, defining approval steps, and configuring actions to be taken at each stage of the workflow.

Other options:

Proposed Accounts Workflow: This is less common, often used to suggest potential accounts during the request or account creation process. It’s not the primary mechanism for making an application available for access requests.

Access Remove Workflow: This workflow is used when access needs to be revoked, not granted. Emergency Access ID Request Workflow: This workflow is specific to requesting temporary, elevated access in emergency situations. It’s not the workflow for general access requests to applications.