Available in v1.0.565

We now support attaching request configurations to multiple groups without duplicating the configuration. If a user is in any of the listed groups, that configuration will be used (according to priority).

Available in v1.0.566

GCP Organizations can now be imported (see docs), allowing users to track and grant organization level roles/users.

Users need to update Opal's service account permissions to include

• resourcemanager.organizations.get
• resourcemanager.organizations.getIamPolicy
• resourcemanager.organizations.setIamPolicy

Available in v1.0.563

Opal's resource "access levels" were renamed to "roles" for clarity and better alignment with our integrations such as GCP, Github, Gitlab etc.

This change does not yet impact APIs

Available in v1.0.563

Previously, Opal would fail to enforce required custom checkboxes in requests. This is now fixed.

Available in v1.0.561

1. Fixed incorrect resources and groups showing up under a reviewer's Items to Review.
2. Fixed incorrect status displayed for some groups under Items to Review.

Available in v1.0.560

Fixed bulk request via bundles not auto submitting with previously filled out request info after a successful MFA redirect.

Available in v1.0.557

Fixed sync error that may occur when forfeiting access to an Okta role.

Available in 1.0.556

1. Users reported being unable to re-assign reviewers. This did not apply to our "bulk assignment" flow. The bug is now fixed.
2. Users reported being unable to submit access reviews. We discovered this bug applied to access reviews in which revocations were applied to deleted resources. The bug is now fixed.

Available in v1.0.551

Added a duration of "90 days" to our request expiration durations and limits/recommendations

Available in v1.0.551

Improved language and editor UI of Opal's visibility options to clarify how the feature works, especially with multi-level visibility options in AWS: