Saviynt SCIP SAVIGA-C01 Question # 16 Topic 2 Discussion

To make an Entitlement request time-bound in Saviynt, the configuration used on the Entitlement Type is D. Start Date/End Date while raising a Request. Here's a breakdown:

Saviynt's Entitlement Management: Entitlements represent specific access rights within an application. Saviynt allows fine-grained control over how these entitlements are requested and granted.

Entitlement Type Configuration: Within Saviynt, each Entitlement Type can be configured with various settings that govern its behavior during access requests.

Time-Bound Access: To enforce time-limited access, Saviynt provides the option to require a Start Date and End Date during the request process.

"Start Date/End Date while raising a Request": This configuration setting, when enabled on an Entitlement Type, forces the requester to specify a desired start and end date for the access. This ensures that the granted access will only be valid for a specific period.

Saviynt's Workflow Engine and Provisioning: When a request with a start and end date is approved, Saviynt's workflow engine will typically handle the provisioning and de-provisioning based on these dates. If connected integration is set up, it may schedule the activation and deactivation of the access in the target system accordingly.

Other Options:

A. Ask for Start Date while revoking: This setting is related to revoking access, not granting time-bound access.

B. Allow update of Access End Date: This allows modification of the end date after the access has been granted, but it doesn't enforce a time-bound request from the outset.

C. Config JSON for Request Dates: While JSON might be used internally for configuration, this is not the specific setting that directly enables time-bound access requests.

In summary: The "Start Date/End Date while raising a Request" configuration on an Entitlement Type in Saviynt is the key to enforcing time-bound access, ensuring that access is granted only for a specific, pre-defined period.