The Project Team
The project team is responsible for managing and executing a particular project within the broader scope of supplier relationship activities. It typically consists of cross-functional members who bring diverse skills and expertise to address the specific objectives of the project.
Similar to Circles, the project team is shaped with roles such as Project Creator, Owner, and Sponsor to define the project's governance and also with different permissions: Admin, Contributor, and Viewer. The users added to the project team will receive notification about the project's progress and activities.
The Project Creator will always receive Admin permissions by default in a project but the rest of the roles are not linked to certain permissions. It is up to the Creator to set which role gets which permission later on when building the project team.
Admins have full editing permissions to the project and team.
Contributors can add activities to the roadmap, post discussion messages, upload attachments, and add/remove team members. They have view-only permission to project details and progress.
Viewers can only post discussion messages and add attachments. They have view-only permission to roadmap, project details, progress, and team.
Anyone who is part of the relationship in which the project is created will automatically have view-only permissions but they will not get any notification about it. You can check who else other than the project team has access to the project by navigating to the Project Team > Relationship Permissions.
Project Invites
By default, users are added directly to a project team and notified that they've been added. However, if a project is looking for a higher level of commitment from the team they can choose to enable the Invites feature.
When enabled new project team members will be sent an invitation along with an onboarding message if they choose to accept the invitation. It's clear from the start what's expected of new team members and helps align the team since everyone gets a chance to show that they're committed to the project and its success.
If a new team member instead declines the invitation they have the option of leaving a message making it clear why they had to decline:
