Skip to main content


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.

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 that they logged to the team will remain after a user is removed.

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. A team member is invited by email by the team admin. 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.

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.


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.

PermissionsView-OnlyTeam MemberTeam Admin
Add team membersX
Remove team membersX
Manage team settingsX

Model Registry

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

PermissionsView-OnlyTeam MemberModel Registry AdminTeam Admin
Add aliasesXXX
Add models to the registryXXX
View models in the registryXXXX
Download modelsXXX
Add/Remove Registry AdminsXX
Add/Remove Protected AliasesX

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


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

PermissionsView-OnlyTeam MemberTeam Admin
View reportsXXX
Create reportsXX
Edit reportsX (team members can only edit their own reports)X
Delete reportsX (team members can only edit their own reports)X


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

PermissionsView-OnlyTeam MemberTeam Admin
View experiment metadata (includes history metrics, system metrics, files, and logs)XXX
Edit experiment panels and workspacesXX
Log experimentsXX
Delete experimentsX (team members can only delete experiments they created)X
Stop experimentsX (team members can only stop experiments they created)X


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

PermissionsView-OnlyTeam MemberTeam Admin
View artifactsXXX
Create artifactsXX
Delete artifactsXX
Edit metadataXX
Edit aliasesXX
Delete aliasesXX
Download artifactXX

System Settings (W&B Server Only)

With system permissions, you have the ability to manage members, create and modify teams, adjust system settings, and view user activity. These privileges enable you to effectively administer and maintain the W&B instance.

PermissionsView-OnlyTeam MemberTeam AdminSystem Admin
Configure system settingsX
Create/delete teamsX
View activity dashboardX

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 is configured 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 would be logged 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 is configured in your environment and the referenced user is part of the service account's parent team.
  • A service account can not be used to log runs to a private project in a team different from its parent team, but it can be used to log runs to public projects in other teams.

Add Social Badges to your Intro

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

Twitter: @weights_biases

For example, to add a Twitter follow badge, add [![Twitter: @weights_biase](]( replacing weights_biases with your Twitter username.

Team Trials

W&B offers free trials for business teams, no credit card required. During the trial, you and your colleagues will have access to all the features in W&B. Once the trial is over, you can upgrade your plan to continue using a W&B Team to collaborate. Your personal W&B account will always remain free, and if you're a student or teacher you can enroll in an academic plan.

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

Privacy Settings

You can see the privacy settings of all team projects on the team settings page:

Advanced Configuration

Secure Storage Connector


W&B does not currently support migrating buckets. More specifically W&B does not support:

  • Migrating from one team-level bucket to another team-level bucket
  • Migrating from a W&B SaaS bucket to a team-level bucket and vice versa.

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.


This feature is only available for Google Cloud Storage buckets and Amazon S3 buckets. Only enterprise teams can use this feature. To learn more about enterprise plans, please contact us at

To provision a cloud storage bucket, we recommend using our secure storage connector terraform module for AWS or GCP.

A cloud storage bucket can be configured only once for a team at the time of team creation. Select External Storage when you create a team to configure a cloud storage bucket. Select your provider and fill out your bucket name and storage encryption key ID, if applicable, and select Create Team.

An error or warning will appear at the bottom of the page if there are issues accessing the bucket or the bucket has invalid settings.

Only organization administrators have the permissions to configure the secure storage connector. The same cloud storage bucket can be used amongst multiple teams by selecting an existing cloud storage bucket from the dropdown.

Was this page helpful?👍👎