Skip to content

Requests

Requests are used to request changes to access controls, such as adding or removing an entitlement, and creating or updating a group.

Requests allow users to request changes to access controls and to make it possible to use Oblique to manage access controls at scale: by managing access to resources, managing teams, and defining owners of objects. They are not intended for administrative management of Oblique, such as adding new integrations. As such, not every change is requestable.

Oblique supports requests for the following changes:

TargetActionDescriptionSupport
UserCREATEImport a user.❌ Unsupported
TeamCREATECreate a team group.✅ Supported
TeamDELETEDelete a team group.⏳ Coming soon
TeamProfileUPDATEUpdate a team group’s description.⏳ Coming soon
TeamMemberCREATEAdd a user to a team group.✅ Supported
TeamMemberDELETERemove a user from a team group.✅ Supported
TeamOwnerCREATEAdd an owner to a team group.⏳ Coming soon
TeamOwnerDELETERemove an owner from a team group.⏳ Coming soon
GroupCREATECreate an attribute-based group.❌ Unsupported
GroupDELETEDelete an attribute-based group.❌ Unsupported
GroupOwnerCREATEAdd an owner to an attribute-based group.⏳ Coming soon
GroupOwnerDELETERemove an owner from an attribute-based group.⏳ Coming soon
ResourceCREATEImport or create a resource.❌ Unsupported
ResourceUPDATEChange a resource’s management mode.❌ Unsupported
ResourceOwnerCREATEAdd an owner to a resource.⏳ Coming soon
ResourceOwnerDELETERemove an owner from a resource.⏳ Coming soon
EntitlementCREATECreate an entitlement.✅ Supported
EntitlementUPDATEEdit an entitlement.✅ Supported
EntitlementDELETERevoke an entitlement.✅ Supported
IntegrationCREATEAdd an integration.❌ Unsupported
IntegrationUPDATEUpdate an integration to allow resource creation.❌ Unsupported
ServiceAccountCREATECreate an API key.❌ Unsupported
ServiceAccountDELETERevoke an API key.❌ Unsupported
AdminCREATEAdd an Admin.❌ Unsupported
AdminDELETERemove an Admin.❌ Unsupported
OwnerUPDATEChange the organization Owner.❌ Unsupported

When creating a request, any required checks will be listed under Review. A check is a requirement for the change request to be applied, and could include an approval from a specific user or group.

By default, a request has a check that requires the change to be approved by the owner of the object being directly affected by the request, or by an Oblique Admin:

  • A request to join or leave a team group needs to be approved by a user who is a team owner or an Oblique Admin.
  • A request to create a team group needs to be approved by a user who is a team owner or an Oblique Admin.
  • A request to grant access to a resource needs to be approved by a user who is a resource owner or an Oblique Admin.

A requestor cannot select themselves as a reviewer. However, if the requestor passes the check requirements for their own request, it will be automatically applied when it is created.

Each check only needs a single approval.

To create a request, navigate to the action you wish to take. There is no separate request page, but rather, access changes will generate a request. As part of the request, you will need to:

  • Fill in necessary information for the request. For example, the team’s name, description, and members for a team group request.
  • Assign reviewers for the request and ensure these reviewers pass the required checks.
  • (Optionally) Disable auto-apply for the request. By default, a request will be automatically applied once all checks pass.

Read the documentation for more detailed instructions for each request type.

When creating a request, checks will be listed under Review.

A reviewer is automatically selected for a check in the following priority order:

  • The requestor, if they have approval permissions
  • An object owner, who is randomly selected if multiple owners exist
  • An Oblique Admin, who is randomly selected if multiple Admins exist

The requestor can change the assigned reviewer by selecting a different person from the list of eligible reviewers. Select the dropdown with the list of reviewers, and then select the desired reviewers.

If the selected list of reviewers is insufficient for the checks, the check will not show an associated reviewer. To add reviewers, select the appropriate reviewer from the list of options under Select reviewers, or choose Add reviewer to add a reviewer for passing each check.

You can add multiple reviewers to a request. You can add or edit reviewers both before and after creating the request.

You can notify reviewers via Slack of new requests assigned to them for review.

You can also copy a link to the request to share with a reviewer out of band:

  1. From the request detail page, select More.
  2. Select Copy link.

Both the requestor and reviewers (including Oblique Admins) can change auto-apply behavior for a request.

You can enable auto-apply for a request until it is approved.

  1. Navigate to the request you wish to enable auto-apply for.
  2. Select Enable auto-apply.

Both the requestor and reviewers (including Oblique Admins) can change auto-apply behavior for a request.

You can disable auto-apply for a request until it is approved.

  1. Navigate to the request you wish to disable auto-apply for.
  2. Next to the Auto-apply badge, select Disable.

You can only approve a request if you have the permissions necessary to approve it. You do not need to be assigned as a reviewer to approve a request.

To approve a request, navigate to the request you wish to approve. You can navigate to a request directly, e.g., from a URL shared with you, or by going to the Requests page and selecting the request from the list.

  1. Review the request from the request detail page. You can see request details including when the request was made, by who, and any required justification or checks. You can see the change details under the Changes tab, and the access changes this will have under the Access Changes tab. You can also see the timeline and summary of the request under Activity.
  2. Select Approve.
  3. (Optionally) Fill in a comment to include with the approval.
  4. Select Approve.

By default, once a request passes all checks, it is automatically applied in your environment.

If auto-apply is disabled, you can apply the request manually:

  1. Navigate to the request detail page.
  2. Select Apply.

You can close a request if it is no longer needed. Both the requestor and reviewers (including Oblique Admins) can close a request.

  1. Navigate to the request you wish to close.
  2. Select More.
  3. Select Close request.

Oblique will automatically close a request if it is obsolete, that is, if it has been made redundant by another request that already makes the same change.

You can see the state of a request in multiple places:

  • On the request detail page, the state is displayed in the header underneath the request title.
  • On the Requests page, the state is displayed in the request row.

The timeline of a request, including open requests, is displayed on the request detail page under Activity. This shows the history of the request, including when it was created, when any changes to the request were made (checks passed or request applied, closed, or marked as obsolete) and by who, and any comments.

You can also see the timeline of requests affecting a user, group, or resource from the user, group, or resource’s detail page.

Changes to the request state are also recorded in audit logs.

You can see requests assigned to you on the Requests page.

The Requests page has three tabs, filtered to show different requests:

  • Todo: Open requests you are a reviewer for
  • Open: All open requests, including both requests you are and are not assigned as a reviewer for
  • Closed: Closed requests