<commit_before>---
categories:
  - "postman"
  - "intro_to_workspaces"
title: "Intro to Workspaces"
page_id: "intro_to_workspaces"
warning: false
---

### What is Workspaces?

A Workspace is an environment where you can perform all your API tasks. It is not a physical container, but a view in the environment. As a result, a collection can exist in different workspaces at the same time.

### Why use Workspaces?

Imagine this scenario. You're working in your own Collections in the Team Library, while collaborating with a few of your teammates. At the team level, a team might be working on different projects in parallel. 




You're  as you work . Then at the team level, 

If a person is on Postman Pro using the Team Library they might be working on their own collections while also collaborating with several others. At the team level, there might be different projects that a team might be working in parallel. One goal that we established upfront was that every team member should have visibility into the team's API infrastructure. Otherwise, it would lead to a situation more like Google Drive where one doesn't know where something is and has to rely on links stored somewhere. While this is helpful, it can be confusing for companies with several teams. The teams might have internal APIs and external APIs for other teams.


To solve these issues, we need a new abstraction - called Workspaces.
 
### Types of Workspaces

Postman offers two types of Workspaces: personal and team. 

* Personal: Individual users can create workspaces that are only visible to them.

* Team: Workspaces shared between all members of a team. All workspaces that a user has visibility into should be accessible from the Postman app and the web
<commit_msg>Update 2018-01-22-intro_to_workspaces.md<commit_after>---
categories:
  - "postman"
  - "intro_to_workspaces"
title: "Intro to Workspaces"
page_id: "intro_to_workspaces"
warning: false
---

### What is Workspaces?

A Workspace is an environment where you can perform all your API tasks. It is not a physical container, but a view in the environment. As a result, a collection can exist in different workspaces at the same time.

### Why use Workspaces?

Imagine this scenario. You're working in your own Collections in the Team Library, while collaborating with a few of your teammates. At the team level, a team might be working on different projects in parallel. 

 Then at the team level, 

If a person is on Postman Pro using the Team Library they might be working on their own collections while also collaborating with several others. At the team level, there might be different projects that a team might be working in parallel. One goal that we established upfront was that every team member should have visibility into the team's API infrastructure. Otherwise, it would lead to a situation more like Google Drive where one doesn't know where something is and has to rely on links stored somewhere. While this is helpful, it can be confusing for companies with several teams. The teams might have internal APIs and external APIs for other teams.


To solve these issues, we need a new abstraction - called Workspaces.
 
### Types of Workspaces

Postman offers two types of Workspaces: personal and team. 

* Personal: Individual users can create workspaces that are only visible to them.

* Team: Workspaces shared between all members of a team. All workspaces that a user has visibility into should be accessible from the Postman app and the web

{'fraction_non_alphanumeric': 0.04051355206847361, 'fraction_numerical': 0.002282453637660485, 'mean_word_length': 4.256371814092954, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, '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': '1561787', 'n_tokens_mistral': 882, 'n_tokens_neox': 813, 'n_words': 547}