<commit_before>---
title: "Collaborating in team workspaces"
updated: 2022-06-15
page_id: "collaborating_in_team_workspaces"
warning: false
contextual_links:
  - type: section
    name: "Additional Resources"
  - type: subtitle
    name: "Videos"
  - type: link
    name: "Working With Your Team in Postman | The Exploratory"
    url: "https://youtu.be/5lscUV-Exac"
  - type: link
    name: "Postman Space Camp | Working with Your Team in Postman"
    url: "https://youtu.be/OifhKJCd_-M"
  - type: subtitle
    name: "Blog Posts"
  - type: link
    name: "Get More Out of Postman by Collaborating with Your Team"
    url: "https://blog.postman.com/get-more-out-of-postman-by-collaborating-with-your-team/"
---

You can use team workspaces to work together on APIs, collections, environments, integrations, mocks, and monitors. Team workspaces can act as a single source of truth for your API projects and encourage collaboration within your team.

[Postman Professional and Enterprise teams](https://www.postman.com/pricing) can also create [private workspaces](/docs/collaborating-in-postman/using-workspaces/creating-workspaces/). A private workspace is a team workspace that's only visible to the user who created it and team members who have been invited to join it. Private workspaces allow teams to restrict access to elements that are relevant only to a particular group.

> Postman creates a default "Team Workspace" for every team. You can rename this workspace, but it can't be deleted.

## Contents

* [Creating a team workspace](#creating-a-team-workspace)
* [Inviting a team member to a workspace](#inviting-a-team-member-to-a-workspace)
* [Moving elements to team workspaces](#moving-elements-to-team-workspaces)
* [Watching team workspaces](#watching-team-workspaces)
* [Next steps](#next-steps)

## Creating a team workspace

You can create a new team workspace at any time by selecting **New** above the sidebar, then **Workspace**. To learn more, see [Creating workspaces](/docs/collaborating-in-postman/using-workspaces/creating-workspaces/).

## Inviting a team member to a workspace

You can invite team members to join a [new](/docs/collaborating-in-postman/using-workspaces/creating-workspaces/) or existing workspace. For more details about how to invite a team member to a workspace, see [Sharing workspaces](/docs/collaborating-in-postman/using-workspaces/managing-workspaces/#sharing-workspaces).

## Moving elements to team workspaces

You can move collections, APIs, and environments to shared workspaces to collaborate with your team.

> You must be an Editor on a collection, API, or environment, the Workspace Admin, or a [Super Admin](/docs/collaborating-in-postman/roles-and-permissions/#team-roles) to move an element to another workspace.

In the sidebar, select the element you want to share, then select the more actions icon <img alt="More actions icon" src="https://assets.postman.com/postman-docs/icon-more-actions-v9.jpg#icon" width="16px"> > **Move**.

Use the search bar to find the workspace to which you want to move the element, or filter by workspace visibility by selecting the icon to the right of the search bar.

You can share elements to personal, private, team, and public workspaces that you have access to.

> You can't move elements from team, private, or public workspaces to a personal workspace.

<!-- -->

> Refer to [Roles and permissions](/docs/collaborating-in-postman/roles-and-permissions/) for information on workspace access control within your team.

Select the workspace, then **Move** (**Collection**, **API**, or **Environment**).

<img alt="Move API" src="https://assets.postman.com/postman-docs/move-api-v9.1.jpg" width="400px"/>

Note that items related to what you're moving won't move with the element automatically:

* **Collections** - Monitors will pause and stay in the current workspace.<commit_msg>add change<commit_after>---
title: "Collaborating in team workspaces"
updated: 2022-06-15
page_id: "collaborating_in_team_workspaces"
warning: false
contextual_links:
  - type: section
    name: "Additional Resources"
  - type: subtitle
    name: "Videos"
  - type: link
    name: "Working With Your Team in Postman | The Exploratory"
    url: "https://youtu.be/5lscUV-Exac"
  - type: link
    name: "Postman Space Camp | Working with Your Team in Postman"
    url: "https://youtu.be/OifhKJCd_-M"
  - type: subtitle
    name: "Blog Posts"
  - type: link
    name: "Get More Out of Postman by Collaborating with Your Team"
    url: "https://blog.postman.com/get-more-out-of-postman-by-collaborating-with-your-team/"
---

You can use team workspaces to work together on APIs, collections, environments, integrations, mocks, and monitors. Team workspaces can act as a single source of truth for your API projects and encourage collaboration within your team.

[Postman Professional and Enterprise teams](https://www.postman.com/pricing) can also create [private workspaces](/docs/collaborating-in-postman/using-workspaces/creating-workspaces/). A private workspace is a team workspace that's only visible to the user who created it and team members who have been invited to join it. Private workspaces allow teams to restrict access to elements that are relevant only to a particular group.

## Contents

* [Creating a team workspace](#creating-a-team-workspace)
* [Inviting a team member to a workspace](#inviting-a-team-member-to-a-workspace)
* [Moving elements to team workspaces](#moving-elements-to-team-workspaces)
* [Watching team workspaces](#watching-team-workspaces)
* [Next steps](#next-steps)

## Creating a team workspace

Postman creates a default "Team Workspace" for every team. You can rename this workspace, but it can't be deleted.

You can create more team workspaces at any time by selecting **New** above the sidebar, then **Workspace**. To learn more, see [Creating workspaces](/docs/collaborating-in-postman/using-workspaces/creating-workspaces/).

## Inviting a team member to a workspace

You can invite team members to join a [new](/docs/collaborating-in-postman/using-workspaces/creating-workspaces/) or existing workspace. For more details about how to invite a team member to a workspace, see [Sharing workspaces](/docs/collaborating-in-postman/using-workspaces/managing-workspaces/#sharing-workspaces).

## Moving elements to team workspaces

You can move collections, APIs, and environments to shared workspaces to collaborate with your team.

> You must be an Editor on a collection, API, or environment, the Workspace Admin, or a [Super Admin](/docs/collaborating-in-postman/roles-and-permissions/#team-roles) to move an element to another workspace.

In the sidebar, select the element you want to share, then select the more actions icon <img alt="More actions icon" src="https://assets.postman.com/postman-docs/icon-more-actions-v9.jpg#icon" width="16px"> > **Move**.

Use the search bar to find the workspace to which you want to move the element, or filter by workspace visibility by selecting the icon to the right of the search bar.

You can share elements to personal, private, team, and public workspaces that you have access to.

> You can't move elements from team, private, or public workspaces to a personal workspace.

<!-- -->

> Refer to [Roles and permissions](/docs/collaborating-in-postman/roles-and-permissions/) for information on workspace access control within your team.

Select the workspace, then **Move** (**Collection**, **API**, or **Environment**).

<img alt="Move API" src="https://assets.postman.com/postman-docs/move-api-v9.1.jpg" width="400px"/>

Note that items related to what you're moving won't move with the element automatically:

* **Collections** - Monitors will pause and stay in the current workspace.
{'fraction_non_alphanumeric': 0.09862060074771174, 'fraction_numerical': 0.004383137811009411, 'mean_word_length': 4.5256410256410255, 'pattern_counts': {'":': 0, '<': 9, '<?xml version=': 0, '>': 18, 'https://': 12, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '835938', 'n_tokens_mistral': 2291, 'n_tokens_neox': 2165, 'n_words': 887}