Skip to content
Edit on GitHub

We have renamed Views to Projects in Iterative Studio.

Accordingly, Views dashboard is now called Projects dashboard; View settings are now called Project settings; and so on.

Teams

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:

Create a team

To create a team, 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. Now, 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.

Invite collaborators

The next step is to invite the team members (or collaborators) for your team. You can also choose to skip adding collaborators at this point. For this, click on Skip and Close on the top right corner. You will be able to add collaborators by accessing team settings later.

If you wish to add collaborators now, enter their email addresses. An email invite will be sent to each invitee.

You can add multiple collaborators. Each collaborator can be assigned the Admin, Edit, or View role. Refer to the Roles section below for more details about the roles.

Once you have added the people that you wish to add to your team, click on Send Invites and Close on the top right corner.

Roles

Team members or collaborators can have the View, Edit or Admin roles. Viewers have read-only access to the projects created by other team members. Editors can create and edit the team's projects. And admins have 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).

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 Admin role.

An additional role Visitor exists for anonymous users who can open a public project.

Privileges to create, open and access the team's projects

FeatureVisitorViewerEditorAdmin
Open a team's projectYes*YesYesYes
Apply filtersYes*YesYesYes
Show / hide columnsYes*YesYesYes
Save the project filters and columns settingsNoNoYesYes
Run experimentsNoNoYesYes
View CML reportsNoNoYesYes
Share a projectNoNoYesYes
Add a new projectNoNoYesYes
Force repository importNoNoYesYes
Delete a projectNoNoYesYes

*Visitors can access only the public projects of the team.

Privileges to manage project settings

FeatureVisitorViewerEditorAdmin
Change project nameNoNoYesYes
Specify project directoryNoNoYesYes
Use existing cloud / data remote credentialsNoNoYesYes
Configure cloud / data remote credentialsNoNoNoYes
Manage mandatory columns (tracking scope)NoNoYesYes
Manage custom filesNoNoYesYes

Privileges to manage the team

FeatureVisitorViewerEditorAdmin
Manage team settingsNoNoNoYes
Manage team collaboratorsNoNoNoYes
Delete a teamNoNoNoYes

Manage your team and its projects

Once you have created the team, the team's workspace opens up.

In this workspace, there are 2 pages - Projects and Settings.

Projects

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 (instructions).

Settings

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.

Additionally, you can also manage connections to self-hosted GitLab servers, edit collaborators and change your team plan.

Manage connections to self-hosted GitLab servers

If your team’s Git repositories are on a self-hosted GitLab server, you can go to the 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.

Edit collaborators

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 members.

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, Teams 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.

Change your team plan and team size

Your team can be in the Free, Basic, Teams 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, Teams or Enterprise plans. A detailed comparison of the different plans can be found in the Iterative Studio pricing page.

  • To upgrade from the Free plan to the Basic, Teams or Enterprise plan or to downgrade your team plan, refer to the section on changing your team plan.

  • To change the number of seats in your Basic plan, refer to the section on changing your team size.

Content

🐛 Found an issue? Let us know! Or fix it:

Edit on GitHub

Have a question? Join our chat, we will help you:

Discord Chat