A New Way To Manage Roles and Permissions
Reimagining roles and permissions is no easy task, but someone had to do it 😎
Authentication, authorization, and access control to a cloud service is an important topic, especially when rolling out in larger enterprises. When we decided to level up the roles and permissions in Crystallize, we wanted to think differently.
How can we make a role-based permission system that is easy to understand and efficient to use?
A Visual Take on Roles and Permissions
The design team has worked closely with the product team to combine the required complexity with an intuitive and visual interface. Resulting in a slick (if I may say so) representation of what a role can access in Crystallize.
The visual dashboard for the roles gives you a quick and visual overview of what users assigned to a role have access to. Much like a talent tree, you have seen in some games. Yes, we love to take inspiration from gaming and consumer-based types of interfaces - even though Crystallize is strictly targeted towards the B2B market.
You can see the new interface below.
Simple Editing of Access Control
We wanted to make the editing process as simple and intuitive as possible. Simply click the concern and the function(s) you want to grant access to, and you are done. For more verbose information, we designed the right sidebar to give you explicit information on the details of the role.
Simple Editing of Access Control
We wanted to make the editing process as simple and intuitive as possible. Simply click the concern and the function(s) you want to grant access to, and you are done. For more verbose information, we designed the right sidebar to give you explicit information on the details of the role.
Fine-grained Control with Conditional Access
In addition to granting access to a specific concern in Crystallize, like publishing items in the catalog tree, you can add conditional access, like in which language and even which part(s) of the tree you have access to create, edit or publish.
To keep it light and in the Crystallize brand, we even decided that a pink mushroom visualizes that there is a condition on a specific concern.
Enter UI Preferences
In addition to having the fine-grained permissions that can be assigned to users, we decided to create a new concept of UI preferences. These settings, per role, affect how the App UI in Crystallize behaves, while the permissions affect the API and the UI.
The case for this is when the editorial teams, e.g., work on different markets and would like to show only the relevant prices for them. The screenshot below shows a UI preference where you cannot see the prices that are in EUR, while you can only see the NOK retail prices but can edit the NOK sales prices.
Also super useful if the retail prices are, e.g., imported from an ERP, and you only want to allow editorial editing of the sales price.
For full details on how to work with the roles and permissions in Crystallize, head over to our R'nP documentation or why not check the LIVESTREAM Roles & Permissions Gamified by Crystallize that's on schedule tomorrow 08/17/2023.
You Should Also Read👇
Authentication vs. Authorization: What's the Difference?
Dive into the intricacies of authentication vs. authorization and learn how these security measures work in tandem to safeguard systems.
Reimagining eCommerce: the Story of Crystallize
Instead of building a better PIM, CMS, eCommerce, or order management service, we wanted to design an API layer you need to market and sell your products on any channel, at any scale, and in any way you want it. A perfect product story engine, if you will.