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:
Then, go through each answer you gave for the questions above and create a new row in the table or specify an existing row based on the information in the answer.For example, from this answer:"There are 2 team managers who review the content and manage metadata. Neither of them, however, manages the navigation. The navigation is only edited by the company’s developers."You can get two rows:
View, edit, create, and delete all content items
Delete, create, edit, and view metadata and navigation items
View, edit, create, and delete all navigation items
This table says that the first role will be able to view, edit, create, and delete all content items except metadata and navigation items. They won't see those at all. The second role will be able to view, edit, create, and delete all navigation items. That means other content items won't be visible to them without stating it in the Cannot do column.