Featuring Painless Access Requests—It All Comes Down to Context

Features at a Glance

Track all requests in one place

In the handy Requests tab, we’ve made it easier to see all requests and their status in a glance.

• The view is split so you can see the requests you’ve made and the requests you have to take action on
• Each request status is indicated by an icon on the right-hand side

‍See the context of requests.

The Requests dashboard makes it easy to get a 360 view around an access request, like:

• Who is requesting something
• Who needs to review a request
• What ticket is linked to the request
• The actions taken related to the request

‍Request access again when it auto-expires.

Use templates to make the same request again.

• Access is set to expire based on a set time or event
• Requests that are expired are marked with a red thumbs down emoji
• Opal saves your request as a template so you can re-use it when you need access again

A Deeper Look at Requests

‍Imagine being able to hit a button and instantly request access to anything from a database, to a Salesforce role, GitHub repo, or Okta group. And track it from start to finish.

Pressing a button to make a request seems simple, but there’s a lot happening behind the scenes.

#1: The Owner

First, Opal makes clear who the request needs to be sent to. ‍

Because of how Opal is structured, a request is immediately sent to the person with the context to approve the request.

#2: High Fidelity

Second, our deep integrations allow us to surface access to resources and more detailed roles within it.

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.

#3: The Life of Access Requests

Third, we believe that most access should be temporary.

‍‍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.