Manage User Roles & Permissions

In order to better manage your team members and ensure that the correct team members have the correct level of access to specific Roadmunk features and actions, we recommend reviewing the different roles that account users can have and the types of permissions that these users can have assigned to them.

Permissions Overview

This role is built for users who only require oversight into products and do not require the ability to build and edit roadmaps (such as director or executive level team members). This role is also well suited for those who provide input into the products in-flight, whether through feedback submission or commenting on active roadmaps (such as customer-facing team members).

This role is the most common for a majority of users, as it provides team members with the tools necessary to build boardroom-ready roadmaps based on team-reviewed, customer-submitted feedback and ideas. 

This role is best suited for administrators or team leaders in an organization who want to onboard their team and manage roadmaps at the departmental level.

The table below shows which user permissions can be assigned to each user role.

User permissions determine how Reviewers, Collaborators, and Account Admins can each interact with a particular roadmap.

Only Collaborators and Account Admins can create and own roadmaps. Every roadmap in Roadmunk has an Owner role, which is automatically assigned to the person who creates the roadmap.

A roadmap Owner can transfer ownership of a roadmap to another Collaborator or Account Admin. Roadmaps can have only one Owner at a time. When ownership is transferred, the original Owner automatically becomes an Editor (see Sharing roadmaps).

• Account Admins - When an Owner shares a roadmap with an Account Admin, the Account Admin is automatically added as an Editor.
• Collaborators - When an Owner shares a roadmap with a Collaborator, they can choose whether to add them to the roadmap an Editor or a Viewer. 
• Reviewers - When an Owner shares a roadmap with a Reviewer, they can only add them to the roadmap as a Viewer. 

Sharing permissions can be edited at any time by the roadmap Owner or by any Account Admin on their account. For more details, check out our article on managing roadmaps.

Roadmap Owners can delete any roadmap they own, while Account Admins can delete any roadmap in their team's Roadmunk account. For more details, check out our article on managing roadmaps.

NOTE: Because of their special permissions, Account Admins can do everything an Owner can do even if the roadmap hasn't been shared with them. 

NOTE: An Editor on a Portfolio Roadmap is only able to edit items rolled-up into the Portfolio from roadmaps that they already own or have permission to edit. Account Admins can do everything an Owner can do even if the Portfolio Roadmap hasn't been shared with them, with the exception of setting and updating sources.

Field permissions determine how Reviewers, Collaborators, and Account Admins can each interact with a particular field. Unlike with roadmaps, users are assigned as Team Members on a specific field. For more details on how fields work in Roadmunk, check out our articles on field management here.

Only Collaborators and Account Admins can be added as Team Members on fields. The person who creates a field will automatically be assigned as a team member on that field.

Sharing Fields with Team Members

Unlike roadmaps, fields can't be shared with Reviewers. They can be shared only with Collaborators and Account Admins in the same Roadmunk account. 

Any user can edit and merge fields they are a team member on.

NOTE: To merge fields, a user must at least be a team member on the source field. If values are added to the destination field as a result of the merge, the user must also be a team member of the destination field (for more details, check out our article on merging fields). 

Any user can delete a field they're a team member on. Account Admins can delete any field in a Roadmunk account, regardless of whether it's been shared with them or not. For more details, check out our article on Promoting & Archiving Fields .