In this post, we take a look at requests in Opal, an essential building block of access management.
In the handy Requests tab, we’ve made it easier to see all requests and their status in a glance.
The Requests dashboard makes it easy to get a 360 view around an access request, like:
Use templates to make the same request again.
Pressing a button to make a request seems simple, but there’s a lot happening behind the scenes.
Because of how Opal is structured, a request is immediately sent to the person with the context to approve the request.
Giving access in a traditional group-based way is typically broad and limited in its usefulness.
For example, it’s the difference between being able to request access to Salesforce versus requesting access to a specific Salesforce role without actually logging in to Salesforce, going to your settings, and adding the person manually.
In other words, access goes through a lifecycle, from Request to Review, Propagation, and eventual Revocation.
In a world where most access is given permanently, it may seem a bit odd to designate a certain death. However, that’s part of Opal’s philosophy that short-lived access, requested only when needed, will help organizations implement dynamic least privilege.
Learn more about how just-in-time access works in Opal.
Want to see it yourself? Contact hello@opal.dev or book a meeting here for a personalized demo.