But how do you decide which permission to assign someone? Often, it helps to think about the person’s existing role in your organization. Ask yourself: what part will they play in this project? What do I need from them?
Here are some examples:
1.) Make someone an editor if you want their help editing and building the board. Say you’re a marketer who’s launching a new campaign. In this context, you might give editor privileges to other marketers who will help you finalize the board’s content and design. When used this way, editor status can be a tool for collaboration, allowing multiple people to put together a single board.
This approach tends to work best in smaller groups. In other words, you don’t necessarily want to make everyone on your team an editor. Otherwise, things can get a little unwieldy! Having a large number of editors can make it harder to keep track of, or maintain control over, everyone’s changes. Instead, some team members might function better as subscribers.
2.) Make someone a subscriber if you want their help sharing the board and tracking activity, but don’t need them to change anything.
For instance, in a campaign, you might assign subscriber privileges to a sales rep who's in charge of sending the board to leads. As a subscriber, they can view notifications and analytics to see which leads are most engaged, helping them determine who they should follow up with. Because they aren’t responsible for the board’s content or design, however, they won’t be able to make any edits.
Note: The same person can be assigned different permission levels for different boards. For example, you could make one of your team members a subscriber for Board A, but an editor for Board B.