Typical use cases

The most common requirements for configuration of users and roles we see are:

• Security
• Content integrity and compliance
• Workflow management
• Localization
• Scalability & maintenance
• Customizing the user experience

This could cover ensuring that only certain users have access to view or update some sensitive content (such as embargoed press releases) and would typically involve defining what actions a user can perform – from full publishing control through to not being able to view the content at all.

In some industries such as the financial and legal sector, accuracy of content is critical. Preventing errors being published is therefore of utmost importance. Configuring roles and permissions to limit who can create, modify or publish information can reduce – or even remove entirely – the risk of inexperienced users publishing incorrect information.

Sometimes it’s necessary for users to have different responsibilities. For instance, a writer could draft content, an editor could review it, and a publisher could review and publish it. Role-specific permissions can streamline and guarantee an effective process.

When you need to publish content in a business serving multiple international markets, it can be useful to control rights for content that belongs to a particular geographic locale. This could be for different translators who speak different languages, or different legal teams who need to ensure compliance in different jurisdictions.

As organizations grow, managing users through roles becomes more efficient - new users can be quickly assigned roles that define their permissions. By controlling what access is given to users, it can become easier to train new users and maintain the system.

If users have certain content that aligns with their responsibilities or interests based on their role, customizing the Sanity Studio to show only content that is relevant for them can reduce complexity and improve their overall user experience.

It might also be relevant to customize the tools, plugins and dashboards available to certain users. For example, a dashboard could show all documents awaiting approval by a publisher – but this might not be relevant for a writer.