- Installing and updating
- Navigating Postman
- Sending your first request
- Managing your account
- Syncing your work
- Discovering templates
- Creating your first collection
- Creating a workspace
- Setting up your Postman app
- Importing and exporting data
- Troubleshooting app issues
- Building requests
- Authorizing requests
- Receiving responses
- Grouping requests in collections
- Using variables
- Managing environments
- Visualizing responses
- Specifying examples
- Using cookies
- Working with certificates
- Generating client code
- Troubleshooting requests
- Scripting in Postman
- Writing pre-request scripts
- Writing tests
- Using the Collection Runner
- Scheduling runs with monitors
- Building request workflows
- Importing data files
- Working with your team
- Defining roles
- Requesting access
- Sharing your work
- Your Private API Network
- Commenting on collections
- Versioning APIs
- Using version control
- Using the API Builder
- Managing and sharing APIs
- Validating APIs
- Monitoring your APIs
- Setting up a monitor
- Viewing monitor results
- Monitoring APIs and websites
- Set up integrations to receive alerts
- Running Postman monitors using static IPs
- Troubleshooting monitors
- Monitoring FAQs
- Analyzing with reports
- Documenting your API
- Authoring your docs
- Publishing your docs
- Viewing documentation
- Using custom domains
- Publishing templates
- Publishing to the API Network
- Submission guidelines
- Managing your team
- Purchasing Postman
- Configuring team settings
- Utilizing audit logs
- Onboarding checklist
- Migrating data between teams
- Intro to SSO
- Configuring SSO for a team
- Logging in to an SSO team
- Microsoft AD FS
- Custom SAML in Azure AD
- Custom SAML in Duo
- Custom SAML in GSuite
- Custom SAML in Okta
- Custom SAML in Onelogin
- Custom SAML in Ping Identity
- Migrating to the current version of Postman
- Developing with Postman utilities
- Postman API
- Echo API
- Collection SDK
- Postman Runtime library
- Code generator library
- Postman Collection conversion
Working with your team
Free collaboration is available in version 6.2 and above.
Postman allows all users to collaborate with their teams through Team Workspaces. Using this feature, you can easily collaborate and share your collections, environments, integrations, history, mocks, monitors, and more.
Postman will alert you with notifications when activities occur within your team and workspace.
Each account can be on one Postman team at a time. Multi-team collaboration and guest accounts are on Postman's roadmap.
- Leaving a team
- Next steps
Create a Team Workspace by inviting a team member to join a personal workspace or create a new one.
Postman creates a default Team Workspace. You cannot delete this workspace but you can rename it.
In Postman, select Invite.
Enter the email address of the individual you’d like to invite to your team workspace, click Add > Invite to team.
The individual will be added to the team once they accept their invitation.
"My Workspace" is a default workspace created by Postman. This workspace is different from other personal workspaces as it cannot be shared with anyone. It cannot be deleted, however it can be renamed. When you invite a teammate to join another personal workspace, Postman converts it into a team workspace.
All members of your workspace will have avatars displayed at the top of Postman. If the avatar is brightly colored, that person is active in the workspace at that time. Hover over an avatar to see the names of the people in your workspace.
Select your current workspace in Postman to open the workspace menu, then click Create New.
Specify a name, a summary, and select Team for type, then invite members to your newly created shared workspace.
Enabling team discovery encourages collaboration and eases the onboarding process by allowing users accessing Postman with their company email address to request to join pre-existing teams within their organization.
You can enable team discovery in the dashboard by selecting Team > Settings, or in the app by selecting Team > Team Settings.
You can optionally add a question for pending team members to provide information when they request to join the team, for any details that will help when approving requests. Enter your question and click Save Question—anyone requesting to join the team will be prompted with the question.
If you do not specify a question, team members can still add a note when they ask to join.
You will receive a notification when anyone makes a request to join the team, including their answer to any question you set, or an optional note.
When you log in to the Postman web dashboard using a verified email address for your company or organization, you can see available teams to join by selecting your avatar > Your Team. You will also be prompted with available teams when you first sign into your Postman account with a verified address.
You will see a list of available teams within your org. Select a team, answer the question set by the team admin if there is one (otherwise you can add an optional note), and click Request to join.
The team administrator will receive a notification that you’ve asked to join the team. Once they approve your request, you will be able to access the team and collaborate on API projects within it.
You can leave a Postman team by navigating to your Postman Dashboard, selecting your avatar in the top-right corner, and clicking Your Team. Click Leave Team.
If you are the last member to leave your team, you will have the option to transfer collections to a personal workspace.
If you are invited to a new team and you are the last in your current team, all team data will be transferred to your personal default workspace.
You can check your usage limits within the Postman app as well as in the dashboard. Free users can select the drop-down menu to the right of Upgrade in the app. Paid users can access the menu by selecting a team name.
The usage menu allows you to review limits for APIs, shared requests and history, mocks, monitors, and public documentation. Click Resource Usage to view your usage period.
Postman archives collections when a free team's collaboration exceeds usage limits. Archived collections cannot be collaborated on, however they are still accessible to users. You will receive an in-app notification when a collection is archived.
Postman chooses which collection(s) to archive based on last edit date. The collections that have gone the longest without a revision will be archived in order to bring your team within usage limits.
Postman indicates the number of archived collections at the bottom of the left sidebar.
To recover archived collections, select Archived Collections.
You will then be able to select Download to retrieve your archived data.
Alternatively, you can download your archived data directly within Postman. To learn how, refer to Settings.
For a more in-depth introduction to workspaces and how they can help organize your API development, check out Creating Workspaces.
To see how you can share the APIs that your teams use internally, check out Your private API Network.