Manage teams

Use W&B Teams as a central workspace for your ML team to build better models faster.

• Track all the experiments your team has tried so you never duplicate work.
• Save and reproduce previously trained models.
• Share progress and results with your boss and collaborators.
• Catch regressions and immediately get alerted when performance drops.
• Benchmark model performance and compare model versions.

Create a collaborative team

1. Sign up or log in to your free W&B account.
2. Click Invite Team in the navigation bar.
3. Create your team and invite collaborators.

info

Note: Only the admin of an organization can create a new team.

Create a team profile

You can customize your team's profile page to show an introduction and showcase reports and projects that are visible to the public or team members. Present reports, projects, and external links.

• Highlight your best research to visitors by showcasing your best public reports
• Showcase the most active projects to make it easier for teammates to find them
• Find collaborators by adding external links to your company or research lab's website and any papers you've published

Remove team members

Team admins can open the team settings page and click the delete button next to the departing member's name. Any runs logged to the team remain after a user leaves.

Team roles and permissions

Select a team role when you invite colleagues to join a team. There are following team role options:

• Admin: Team admins can add and remove other admins or team members. They have permissions to modify all projects and full deletion permissions. This includes, but is not limited to, deleting runs, projects, artifacts, and sweeps.
• Member: A regular member of the team. An admin invites a team member by email. A team member cannot invite other members. Team members can only delete runs and sweep runs created by that member. Suppose you have two members A and B. Member B moves a Run from team B's project to a different project owned by Member A. Member A can not delete the Run Member B moved to Member A's project. Only the member that creates the Run, or the team admin, can delete the run.
• Service (Enterprise-only feature): A service worker, an API key useful for using W&B with your run automation tools. If you use the API key from a service account for your team, make sure to set the environment variable WANDB_USERNAME to attribute runs to the correct user. See more on the relevant behavior below.
• View-Only (Enterprise-only feature): View-Only members can view assets within the team such as runs, reports, and workspaces. They can follow and comment on reports, but they can not create, edit, or delete project overview, reports, or runs. View-Only members do not have an API key.
• Custom roles (Enterprise-only feature): Custom roles allow organization admins to compose new roles by inheriting from the above View-Only or Member roles, and adding additional permissions to achieve fine-grained access control. Team admins can then assign any of those custom roles to users in their respective teams. Refer to this article for details.

note

W&B recommends to have more than one admin in a team. It is a best practice to ensure that admin operations can continue when the primary admin is not available.

note

If you're on W&B Server (Dedicated Cloud or Self-managed deployment), you will need a updated enterprise license to use the Custom Roles feature.

Team settings

Team settings allow you to manage the settings for your team and its members. With these privileges, you can effectively oversee and organize your team within W&B.

Permissions	View-Only	Team Member	Team Admin
Add team members			X
Remove team members			X
Manage team settings			X

Model Registry

The proceeding table lists permissions that apply to all projects across a given team.

Permissions	View-Only	Team Member	Model Registry Admin	Team Admin
Add aliases		X	X	X
Add models to the registry		X	X	X
View models in the registry	X	X	X	X
Download models	X	X	X	X
Add/Remove Registry Admins			X	X
Add/Remove Protected Aliases			X

See the Model Registry chapter for more information about protected aliases.

Reports

Report permissions grant access to create, view, and edit reports. The proceeding table lists permissions that apply to all reports across a given team.

Permissions	View-Only	Team Member	Team Admin
View reports	X	X	X
Create reports		X	X
Edit reports		X (team members can only edit their own reports)	X
Delete reports		X (team members can only edit their own reports)	X

Experiments

The proceeding table lists permissions that apply to all experiments across a given team.

Permissions	View-Only	Team Member	Team Admin
View experiment metadata (includes history metrics, system metrics, files, and logs)	X	X	X
Edit experiment panels and workspaces		X	X
Log experiments		X	X
Delete experiments		X (team members can only delete experiments they created)	X
Stop experiments		X (team members can only stop experiments they created)	X

Artifacts

The proceeding table lists permissions that apply to all artifacts across a given team.

Permissions	View-Only	Team Member	Team Admin
View artifacts	X	X	X
Create artifacts		X	X
Delete artifacts		X	X
Edit metadata		X	X
Edit aliases		X	X
Delete aliases		X	X
Download artifact		X	X

System settings (W&B Server only)

System permissions allow you to manage members, create and modify teams, and adjust system settings. These privileges enable you to effectively administer and maintain the W&B instance.

Permissions	View-Only	Team Member	Team Admin	System Admin
Configure system settings				X
Create/delete teams				X

Team service account behavior

• When you configure a team in your training environment, you can use a service account from that team to log runs in either of private or public projects within that team. Additionally, you can attribute those runs to a user if WANDB_USERNAME or WANDB_USER_EMAIL variable exists in your environment and the referenced user is part of that team.
• When you do not configure a team in your training environment and use a service account, the runs log to the named project within that service account's parent team. In this case as well, you can attribute the runs to a user if WANDB_USERNAME or WANDB_USER_EMAIL variable exists in your environment and the referenced user is part of the service account's parent team.
• A service account can not log runs to a private project in a team different from its parent team. A service account can log to runs to project only if the project is set to Open project visibility.

Add social badges to your intro

In your Intro, type / and choose Markdown and paste the markdown snippet that renders your badge. Once you convert it to WYSIWYG, you can resize it.

For example, to add a Twitter follow badge, add [![Twitter: @weights_biase](https://img.shields.io/twitter/follow/weights_biases?style=social)](https://twitter.com/intent/follow?screen_name=weights_biases replacing weights_biases with your Twitter username.

Team trials

See the pricing page for more information on W&B plans. You can download all your data at any time, either using the dashboard UI or the Export API.

Privacy settings

You can see the privacy settings of all team projects on the team settings page: app.wandb.ai/teams/your-team-name

Advanced configuration

Secure storage connector

The team-level secure storage connector allows teams to use their own cloud storage bucket with W&B. This provides greater data access control and data isolation for teams with highly sensitive data or strict compliance requirements. Refer to Secure Storage Connector for more information.