You can create teams with one or more team members. The team members are also called collaborators, and you can assign different roles to them. The projects that you create in your team's page will be accessible to all members of the team.
In this page, you will learn about:
- How to create a team
- How to invite collaborators (team members)
- The privileges (access permissions) of different roles
- How to manage the team and its projects
- How to manage connections to self-hosted GitLab servers
- Why and how to change your team plan and team size
Click on the drop down next to
Personal. All the teams that you have created
so far will be listed within
Teams in the drop down menu. If you have not
created any team so far, this list will be empty.
To create a new team, click on
Create a team.
You will be asked to enter the URL namespace for your team. Enter a unique name. The URL for your team will be formed using this name.
Then, click the
Create team button on the top right corner.
To add collaborators, enter their email addresses. Each collaborator can be
assigned the Admin, Edit, or View role. An email invite will be sent
to each invitee. Then, click on
Send invites and close.
You can also click on
Skip and close to skip adding collaborators while
creating the team, and
add them later by accessing team settings.
Team members or collaborators can have the following roles:
Viewershave read-only access to the projects created by other team members.
Editorscan create and edit the team's projects.
Adminshave full access to the team's projects and settings. They can add (invite) and remove collaborators as well as change team settings such as cloud credentials (data remotes).
- An additional role
Visitorexists for anonymous users who can open a public project.
Iterative Studio does not have the concept of an
Owner role. The user who
creates the team has the
Admin role. The privileges of such an admin is the
same as that of any other collaborator who has been assigned the
If your Git account does not have write access on the Git repository connected
to a project, you cannot push changes (e.g., new experiments) to the repository
even if the project belongs to a team where you are an
|Open a team's project||Yes*||Yes||Yes||Yes|
|Show / hide columns||Yes*||Yes||Yes||Yes|
|Save the project filters and columns settings||No||No||Yes||Yes|
|View CML reports||No||No||Yes||Yes|
|Share a project||No||No||Yes||Yes|
|Add a new project||No||No||Yes||Yes|
|Force repository import||No||No||Yes||Yes|
|Delete a project||No||No||Yes||Yes|
*Visitors can access only the public projects of the team.
|Change project name||No||No||Yes||Yes|
|Specify project directory||No||No||Yes||Yes|
|Use existing cloud / data remote credentials||No||No||Yes||Yes|
|Configure cloud / data remote credentials||No||No||No||Yes|
|Access a team's models dashboard||No||Yes||Yes||Yes|
|Access a team's model details page||No||Yes||Yes||Yes|
|Perform model actions in the team's model registry|
- add / deprecate models
- register / deregsiter versions
- assign / unassign stages
*All team members can submit model actions in Iterative Studio. But for a team member's actions to successfully complete, the team member must have write access in the Git repository from where the model was added. This is because any model action constitutes writing a Git commit, pull/merge request or tag to the Git repository. If the team member does not have this write access, then the model action will fail.
|Manage team settings||No||No||No||Yes|
|Manage team collaborators||No||No||No||Yes|
|Manage team plan and billing||No||No||No||Yes|
|Delete a team||No||No||No||Yes|
Once you have created the team, the team's workspace opens up.
This is the projects dashboard for the team. All the projects on this dashboard are accessible to all members (collaborators) of the team.
To add a project to this dashboard, click on
Add a project. The process for
adding a project is the same as that for adding personal projects
This is the models dashboard for the team. All the models on this dashboard are accessible to all members (collaborators) of the team.
To add a model to this dashboard, click on
Add a model. The process for adding
a model is the same as that for adding personal models
In the team settings page, you can change the team name, add credentials for the data remotes, and delete the team. Note that these settings are applicable to the team and are thus different from project settings.
If your team’s Git repositories are on a self-hosted GitLab server, you can go
GitLab connections section of the team settings page to set up a
connection to this server. Once you set up the connection, all your team members
can connect to the Git repositories on this server. For more details, refer to
Custom GitLab Server Connection.
To manage the collaborators (team members) of your team, go to the
Collaborators section of the team settings page. Here you can invite new team
members as well as remove or change the roles of existing team
The number of collaborators in your team depends on your team plan. By default, all teams are on the Free plan, and can have 2 collaborators. To add more collaborators, upgrade to the Basic or Enterprise plans.
All collaborators and pending invites get counted in the subscription. Suppose you have subscribed for a 10 member team. If you have 5 members who have accepted your team invite and 3 pending invites, then you will have 2 remaining seats. This means that you can invite 2 more collaborators. At this point, if you remove any one team member or pending invite, that seat becomes available and so you will have 3 remaining seats.
Your team can be in the Free, Basic or Enterprise plan. All newly created teams are on the Free plan. This plan is designed for teams that are starting out: you can invite one other team member and import as many repositories as you want. For more advanced collaboration, you can switch to the Basic or Enterprise plans. A detailed comparison of the different plans can be found in the Iterative Studio pricing page.