Ticket Propagation
Sometimes after a user is approved or revoked for access within an end system, there is additional manual work needed to provision or update their access. In these cases Opal customers will leverage their IT or operations teams to finish the process.
Using Opal, these teams can gain visibility into what access needs to be manually provisioned and track the status of the manual provisioning.
In the example below, we are looking at a Figma application.
On the left side of the above screenshot, you can see that the ticket provider toggle is turned on. Once enabled, you have the option to create a ticket when access is approved, when access is taken away, or both.
Once the criteria (approval and/or revocation) are met, then a ticket will be created. The ticket includes information about the requestor and the resource being requested and will be sent to the ticketing environment in the linked productivity integration.
Updated about 1 month ago