Release Notes September 2024
  • 24 Sep 2024
  • 3 Minutes to read
  • Dark
    Light
  • PDF

Release Notes September 2024

  • Dark
    Light
  • PDF

Article summary

Here is a glimpse of what you can expect to see in Clarity’s 1.6.0.1 September update.

If you only read one thing: Dynamic Tagging!

Dynamic (and Static) Tagging

Clarity is excited to announce a major improvement to our tagging capabilities.

Tagging is a foundational capability in Clarity that allows you to group and manage disparate records.Tags allow you to control the scope of access reviews and customize lifecycle management conditions. While Clarity’s current tagging is a powerful tool, the manual nature of maintaining tags has made them impractical in larger, ever changing environments.

Thus, we decided to overhaul the creation, application, and maintenance of Tags! Our new “Tag Builder” allows you to use a data-driven approach to create Static and Dynamic filters that determine which Applications, Identities, Entitlements and Roles will be tagged.

How it works:

First, Tags is now on the left-hand Navigation Menu. You can either edit your existing tags or use the New Tag Builder to create new ones!  

After clicking on the New Tag Builder button, you can select what type of “entity” you want to tag, then select Static or Dynamic tags.

  • Dynamic tags will automatically tag new records that match whenever they are created or updated

  • Static tags will tag everything “right now” and not update based on future changes

Screenshot 2024-09-13 at 4.32.45 PM

After clicking Next, you can set your tag filters.

After clicking apply, you can see the list of entitlements that match your designated filter.

Once a tag is created, you can easily review all the entities associated with that tag.

Screenshot 2024-09-13 at 4.37.50 PM

Role Change Access Request - Self Service

Role Based Access Control (RBAC) is one of the best methods for improving access reviews and lifecycle management. However, long term maintenance of Roles can be difficult. The difficulty stems from ever-changing IT access requirements driven by new applications, projects, and company direction.

Clarity recognized this pain and heard your feedback. “The business needs to be able to request changes to a role.”

Our solution was to expand the request capabilities within the Self Service Portal.

Managers and leaders can now ask for roles to be Created, Expanded, or Deleted. Allowing these users to request changes means IT teams don’t need to wait for the “perfect” RBAC structure to be created.  

Here’s how it works:

Step 1: Make a Request

Step 2: Select the Role

Step 3: Select the Entitlements needed (this is just like our existing Access Request flow - so it should be familiar to current Clarity users.)

Screenshot 2024-09-13 at 2.21.56 PM

Step 4: Wait for the request to be approved!

Screenshot 2024-09-13 at 2.22.09 PM

If you are leveraging RBAC to do either of the below:

  • Reduce the scope of your active UAR’s by removing birthright access

  • Automate onboarding and off-boarding for your teams

This opens up a direct feedback loop from your business to ensure they have the right access when they need it, without yet another meeting!


UX Improvements

Improved Dashboard Styling and Layout

Screenshot 2024-09-13 at 1.52.24 PM

Improved Identity Title Bar Layout

Screenshot 2024-09-13 at 4.16.26 PM

Improved Application Title Bar Layout

Screenshot 2024-09-13 at 4.15.26 PM

Improved Integration Data Pipeline Stability

We’ve redesigned how data is pulled from downstream applications to significantly reduce the number of API calls and database updates performed during a sync.

  • Impact: There are significantly fewer errors, fewer incomplete syncs, fewer sync timeouts, and overall much improved data pipeline stability.  Lower database load also has incremental application performance improvements while syncs are active.  

New and Improved Integrations

- Improved connector for Oracle Cloud Fusion ERP (Now supports UAR + LCM).

- Box Enterprise (Supports UAR + LCM)

Important Bugs Resolved:

  • Azure RBAC was creating duplicate entitlements, the incorrect unique identifier issue was resolved, and the duplicates were removed

  • Merging identities was not removing the “old” identity - this has now been resolved

  • Improved report load times - as part of the data pipeline stability improvements, we expect report performance improvements.


Was this article helpful?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.