User roles

Learn to create user roles to limit end-users' access to boards, changelogs, and more.

MP

Written By Markus Palm

Last updated 2 days ago

Learn how to create user roles to limit end-users' access to boards, changelogs, and more. User roles allow you to manage multiple unrelated products under the same public portal while showing end-users only what’s relevant to them.

This feature is available on our Enterprise plan.


Creating user roles

  1. Go to Settings → User Roles

  2. Click on Add Role on the top right

  3. Enter a name for the role, such as ‘Product A users

  4. Click on Create role


Assigning roles to users

1. Add user roles manually

While not intuitive at scale, you can assign user roles manually to users:

  1. Go to Dashboard → Users

  2. Use the search bar to enter the user's name, email, or company

  3. Click on the user to open their profile

  4. From the User role toggle, select the desired role

2. Add user role via API

  1. Go to Settings → API to copy the API key

  2. Then, follow our API documentation to assign the user roles

3. Add user roles via SSO

To add user roles via SSO, start by:

  1. Set up our SSO by following this guide:

  2. When you’ve completed that, modify the JWT body to include the user role:

{
name: "Jane Doe",
email: "jane.doe@example.com",
role: "Member" // Change this to the role you want to add the user
}

👨‍💻 You'll need to write custom code for adding users through API and SSO. If you're uncomfortable with this, share these guides with a technical team member who can assist.


What you can do with user roles

1. Role-based access to feedback boards

If your company has multiple different products that are not relevant to each other, you can make feedback boards visible only to certain user roles.

This allows you to have one public portal for your company and control which users see feedback boards for specific products.

Learn to set it up from here:


2. Role-based access to changelog

In addition to restricting board access, you can also create separate changelog releases that are only visible to selected user roles. This ensures that end-users only see updates relevant to their role.

Learn to set it up from here:


More on user roles:


FAQ