Team members are the users who will assist in the creation of the contract.
Project team consists of Project Groups. Each project group has different roles, which specify the permissions for the users in that group such as:
- Ownership
- Visibility
- Editing Capabilities
- Review and Approval

A project team consists of project groups. Each project group has different roles, which specify the permissions for the users in that group. The permissions specify the objects the users can access and what actions the users can perform in that project.
Creating groups with different roles enables you to assign users to the project team with different roles and capabilities. Membership in a project group allows users to perform certain tasks at a project level, not a global level. If you want to give a large group of people access to a project, set the access control rather than adding them as team members. Add people as team members if you have a small group of people who need to receive notifications and participate in the project.
Note
The project groups in the Team tab are different from the groups you add using the option Manage → Administration.
Generally, SAP Ariba Contracts templates will be set up with all the necessary project groups. Some project groups may have some members already assigned. Most of the time, contract workspace owners will not have to create new project groups, but they will need to assign members to the existing project groups.
Non-Team Member Involvement
Workspace owners may assign tasks to users who do not belong to any of the project groups. In this scenario, depending on the access settings for the entire workspace, these non-team members may not be able to view the entire workspace. Their view might be limited to the specific task(s) they have been assigned. For example, a reviewer or approver of a document may only see that review or approval task and the linked document without being able to access the workspace in its entirety. It is also possible to include people who don’t even have system access. Email reviewers who receive information via email depend on another user with access to SAP Ariba Contracts to communicate their responses back into the workspace on their behalf. This is useful when negotiating with the other contract party who may not have direct system access.