← Back to Chapters

Workspaces & Collaboration in Postman

? Workspaces & Collaboration in Postman

? Quick Overview

Postman Workspaces allow users to organize API requests, environments, collections, and documentation in a structured way. Workspaces can be created for individual use or shared with a team to collaborate on API development and testing.

? Key Concepts

  • Personal Workspaces are private and visible only to the owner
  • Team Workspaces enable collaboration with shared access
  • Roles control who can view, edit, or manage resources
  • Changes sync automatically across team members

? Syntax / Theory

A workspace in Postman is a container for API-related assets. Each workspace can include collections, APIs, environments, mocks, and monitors. Switching between workspaces helps isolate projects and avoid conflicts.

? Code Example(s)

? View Code Example 
// Example of a request stored inside a workspace collection
GET https://api.example.com/users
// Headers and authorization are shared via the workspace
Authorization: Bearer {{token}}

? Live Output / Explanation

What Happens?

When this request is executed inside a workspace, all team members with access can see the request, reuse the environment variables, and view the response history if permissions allow.

? Interactive Example

Workspace Visibility Simulator

Toggle the workspace type to see how data access changes for your team.

Admin (You)
Access: Full
Collaborator
Access: Denied
? View Interactive Demo Code 
// Simple SVG diagram showing workspace separation
<svg width="300" height="120">
<rect x="10" y="20" width="120" height="60" fill="#2563eb"/>
<text x="20" y="55" fill="#ffffff">Personal</text>
<rect x="160" y="20" width="120" height="60" fill="#16a34a"/>
<text x="180" y="55" fill="#ffffff">Team</text>
</svg>

? Use Cases

  • Solo developers testing APIs in Personal Workspaces
  • Teams collaborating on microservices using Team Workspaces
  • QA teams sharing test collections with developers
  • Maintaining separate workspaces for dev, staging, and production

? Tips & Best Practices

  • Use Personal Workspaces for experiments and drafts
  • Create Team Workspaces for shared, production-ready APIs
  • Define clear roles to avoid accidental changes
  • Name workspaces clearly to reflect their purpose

? Try It Yourself

  1. Create one Personal Workspace and add a sample request
  2. Create a Team Workspace and invite a collaborator
  3. Compare visibility and permissions between both
  4. Move a collection from Personal to Team Workspace