Design roles
When identifying roles, it’s essential to have a clear understanding of the users’ responsibilities. By designing such roles for your projects, you’ll be able to clarify what each role is accounted for and what their main tasks are.
Let’s design the role table
When designing roles, take your content model into account as well.
Let's design the roles using a table to visualize how the roles would look. If suitable, modify the model to reflect the creation flow. The goal is to create a three-column table like this:
Role | Can do | Cannot do |
Role | Can do | Cannot do |
Team manager | View, edit, create, and delete all content items | Delete, create, edit, and view metadata and navigation items |
Developers | View, edit, create, and delete all navigation items |
Role naming
There are multiple approaches you can choose from. You can pick what will serve your company the most. For example, it can mimic your RBAC model
; it can be loosely based on the people's positions in the organization or express the permissions that roles possess. You can also use a hybrid naming where you combine more approaches.