# Team namespaces Every [team](/studio/teams) has a namespace of its own, and releases published under it belong to the team. A reference like `smith-lab/cell-cycle@1.2.0` resolves the same way as a personal one. On the Hub, the team's name appears next to the namespace. ## Who can publish | Role | Private releases | Public releases | | --- | --- | --- | | Viewer | No | No | | Member | Yes | No | | Admin, Owner | Yes | Yes | Private team releases are visible to every member of the team, and to no one else. Someone who leaves the team loses access to them, including the ones they published. ## Publishing under the team **From Studio.** A lab that belongs to the team publishes under the team's namespace. Switch to the team, or [transfer the lab](/studio/teams#work-in-a-team) into it first. **From the CLI.** Name the team's namespace in the reference: ```bash biosimulant labs publish ./cell-cycle smith-lab/cell-cycle@1.2.0 ``` A key made for the team with `biosimulant auth login --web` publishes a bare name under the team's namespace, and can't publish under yours. See [CLI sign-in](/cli#sign-in). **From Desktop.** When you belong to teams, the publish dialog asks **Publish as**. Pick the team. **From an agent.** An agent connected for the team publishes its workspaces under the team's namespace. See [Connect your agent](/agents/connect#connect-for-a-team). If the lab's `lab.yaml` names a namespace in its `package` field, it must be the one you're publishing under. ## Pulling private team releases Members pull private team releases with their own credentials, exactly like their own private releases: ```bash biosimulant labs pull smith-lab/cell-cycle@1.2.0 ``` ## Adopting your namespace If you have been publishing under your personal namespace and want those releases to become the team's, an Owner can give the team that namespace. On the team's **General** tab, under **Use your personal namespace**, choose **See what would move**. Studio lists the labs and private releases that will move, and asks you to type the namespace to confirm. This works only while the team hasn't published anything under its own namespace yet. After adoption: - existing references such as `ada/cell-cycle@1.2.0` resolve exactly as before, and their Evidence Passports still verify; - private releases become visible to every team member; - your labs published under that namespace move to the team; - you get a new personal namespace for anything you publish on your own. **Warning:** Adoption is one-way. Handing the namespace back to a person needs Biosimulant support. ## Next steps - [Teams](/studio/teams): roles, credits and keys - [Package and publish](/hub/publish): cutting a release - [Visibility and sharing](/hub/visibility): who can see what