Skip to main content
Skip table of contents

Managing Client and Project Teams

Organizations that have a large number of users involved in reviewing content can define teams to help control who should be involved in which projects. 

Why to Use Client or Project Teams

Setting up a Client or Project Team has two primary benefits: 

Limits the visibility and access of users to specific projects - If Teams are used, then collaborators will only be able to see and create new Reviews for projects that include them on the Team. Collaborators will not be able to see any users in the organization who are not included with them on their Teams. 

Automatically adds users to Review share lists - Any new Reviews created for a Project with a Team will automatically have the people on the Team added to the share list for the Review. The creator does not have to spend time searching through a long list of people and individually adding those who should normally be included. 

Defining Teams

Teams can be defined at either the Client level or the Project level. If a Team is defined at the Client level then that Team will automatically apply to all Projects created for that Client.  

(Note that if you are organizing Projects by a category other than by Client, then the “Client” teams referred to in this article will refer to teams for that category instead).

To define a Client or Project Team: 

  1. Go to Settings > Clients, or  Settings > Projects. 

  1. Click on the + button next to a Client or Project name. 

  1. Use the dropdown menu to select the users you wish to add to the Team.

  1. To delete a user from the Team, click on the red X button next to their name.  

Rules for Using Client or Project Teams

When using Client or Project Teams there are a few other rules that also come into play: 

If a Team is defined at the Client level, then any project associated with that Client will inherit the same Team.

If a Team is also defined at the Project level for a Client that already has a Team, the Project Team will take precedence over the Client Team. 

When Teams are used, then Collaborators can only create Reviews for Projects that include them on the Team. And they can only share those Reviews with other members of those Teams. Admins, on the other hand, are free to share any Review from any Project with any user regardless of whether a Team exists for that Project or not.  

Note that when changing the makeup of a Team it does not change the current sharing list of any Reviews that may already exist. 


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.