We are pleased to announce that the Splunk Observability Cloud platform will now offer additional Role-Based Access Control roles for more restrictive functional control across the platform.
In addition to existing admin and user roles, we are launching “read_only” and subscription “usage” roles. “Read_only” will provide viewing-only privileges while the “usage” role will grant users the ability to access subscription data without the need to be full-fledged admins. Now you get more flexibility when it comes to choosing the right roles for your users!
Key features include:
-
Introducing a new capability-based RBAC framework with new “read_only” and “usage” roles along with existing Admin and User roles
-
New APIs to assign users with roles
-
APIs will honor capabilities based on their role defined to their token; For e.g. User Tokens will inherit individual users' role capabilities and org tokens can be assigned with an available predefined role
Both new roles will be automatically available for all Splunk Enterprise customers this week.
Along with this release, we wanted to notify our users of a change in our naming nomenclature: we are renaming the existing “User” Role to “Power” Role. The role name change will occur by the end of the February 5th week. You can find more details on this change in our community post here
Thank you for being a loyal Splunk customer!
