Associating Users With Teams and Projects

Administrators can associate users with teams and projects in the system.

  • Associating users with teams is a convenient way to set the same permissions for a group of people. It also makes it easy to send messages to those who are designated as authors on the license. Also, if you intend to have private output (i.e., output where users must log in), it is necessary to associate those users (authors, SMEs, or viewers) with a team, and then associate that team with the appropriate site.
  • Associating users with projects gives those users access to specific projects. Without access to a project, a user—even an administrator—cannot open that project to view it or work in it. You can only associate authors with projects; you cannot associate SMEs or viewers with projects.

Permission Required?

For this activity, you must have the following permission setting:

For more information about permissions, see Setting User Permissions or Setting Team Permissions.

How to Associate Users With Teams and Projects

The following steps show how to make associations in the user profile. However, you can also open the project profile or team profile and do the same.

  1. Make sure you have already created the team(s), created the project(s), or uploaded the project(s).
  2. On the left side of the interface, click Users.
  3. Click the user’s avatar or name.
  4. On the left, click Access.
  5. Click Edit.
  6. In the Teams section, you can you can associate teams with a user.
  7. In the Projects section, you can associate projects with an author.
  8. Click Save.

Note Associations between users, projects, and teams are treated separately. Therefore, if one connection is severed, another one remains.

For example, let's say you open a team and associate it with a user and a project. This means that both the user and project are associated with that team, but the user is not automatically associated with the project. You need to manually associate the user with the project. This is an extra step, but if you then remove the user from the team, that person is still connected with the project.

Note If your license is enabled for single sign-on (SSO) and you have private output, you can automate the process for inviting users (as viewers), as well as associating users and sites with a team. In the license settings, you can use an option to create viewer users on demand, and choose one or more teams to associate with that process. By simply providing new users with the link to the private output, they will be onboarded with the viewer seat type and added to the team(s) you designate. See Single Sign-On, Creating Viewer Users On Demand, and Onboarding Users With Single Sign-On.