Creating a Custom Role

For small teams and projects, our default user roles (Admin, Editor, and Writer) should be sufficient. However, there are many scenarios where you might need a custom role for your project. This article will help you create a custom role from scratch the right way.

Creating a Custom Role

To create a custom role, go to the Roles page, which you can access in the account level menu.

Once you're on the Roles page, find and click the Add new role button.

A field for your new role will appear. Give it a name and a description, then click the save icon.

You've successfully created a new role!

But right now, it doesn't do anything. You need to give it permissions first.  All you need to know about permissions are discussed in this article.

Now, assuming you've already given the correct permissions you want for your new role, it's time for the next step: assigning this role to a user.

Assigning the Custom Role to a User

To assign a custom role to a user, go to the Users page, which can be accessed in the account-level menu.

Once you're on the User's page, find the user you want to assign the custom role to, then:

  1. Click the corresponding Edit button under the Actions column.
  2. A window containing the user's data will show up.
  3. Under the role dropdown, select your new custom role.
  4. After that, click Save at the bottom of the window and you're done!

Your custom role is all set up, but it's not yet fully ready. There's one last step you need to do.

Assigning the Custom Role to a Workflow

You've created your custom role and assigned it to a user. But something is wrong.

Based on the permissions you've given it, the user with your new custom role should be able to claim a task or edit a task once it reaches a certain workflow. But why can't the user with your brand new custom role claim a task or edit an assignment?

The reason behind this, even if you gave the correct permissions, is because your custom role is not assigned to a workflow status. You need to assign it to one first. See "Why can't I assign a user to a brief?" to fix this problem.