We’re thrilled to be moving more and more of our customers over to Advanced Permissions, which unlock deeper levels of governance with customizable permissions and restrictions within your Creator Studio (our name for “new” Studio moving forward!). We also want to thank our customers for helping our teams as we quickly work to enhance the experience and resolve a few known issues. Our product and engineering teams have shifted dedicated resources to focus on Advanced Permissions as a priority item. We appreciate your continued feedback during this process!

Known Functionality Limits and Resolutions

Inability to bulk edit Advanced Permissions roles

This includes the ability to bulk assign users to manage a topic, bulk assign new templates, make bulk changes to roles, and assign new email aliases and author aliases.

Inability to pull specific reports based on permissions

this includes the ability to view filters such as:

• Show me everyone who has access to a particular group
• Show me everyone who has access to a particular template
• Show me everyone who has access to a particular topic
• Show me everyone who has access to a particular email alias
• Show me all content publishers who don’t have a topic assigned

Resolutions

Our teams have already kicked off bulk updates and reporting work and expect for the first phase of these engineering efforts to take just a few weeks to complete. This first iteration will allow for reporting and bulk updates via our internal API, meaning, our professional services teams will be able to accomplish bulk updates and pull Advanced Permissions reports on behalf of our customers. Following this sprint work, our teams will immediately begin on the second iteration which will include updates to the User Interface so customers will be able to self-service bulk updates for their user roles and view relevant reports. This second phase of work will also include restriction filters on the Users page itself so that customers can easily see specific permissions, restrictions, topics, etc., on an individual user level.

Inability to impersonate different roles

This use case would allow specific roles to be able to “impersonate” another user so they would be able to experience what the user can see and do within Studio based on their permissions.

Resolutions

Impersonation or viewpoints into another user’s experience is not something we currently provide in our product and is potentially a large technical undertaking. Our product and engineering teams are looking into this possibility for the future, but for now, we hope the reporting coming in a few weeks that will show permissions and restrictions per individual users can help with this use case while we work to solve this.