Early Access feature
Postman Organizations streamline API collaboration, reduce clutter in teams, maintain tighter access controls, and prevent the unwanted exposure of work and secrets. Organizations enable you to replicate your internal structure by creating independent teams, each with its own set of managers and members. This setup prevents sharing sensitive information and gives each team better control over its membership.
Organization Teams can directly invite other Teams to collaborate or consume the Teams' content, improving collaboration scaling. By default, a given Organization Team's content is shared with the entire Organization. However, content sharing can be limited to just the team or specific team members, helping to reduce clutter and oversharing in your Organization.
Tip: Plan your Organization setup
Before you set up your Organization Teams, consider the following:
- How many teams do you need and for which specific step in your API lifecycle?
- How will you name your teams and workspaces?
- Who will be on each team, and who will manage it?
- How many workspaces will each team need to begin collaborating?
- If you have Slack or Teams workspaces, which channels do you need to connect each workspace to post workspace updates?
Organization Managers are responsible for creating Teams in the Organization and can manage any Team. They're also responsible for assigning individual Team Managers to the teams they create.
Team Managers can approve the adding of Members and the sharing of content from the Teams they manage.
Collaborators can be brought into the team as secondary contributors or consumers. For example, collaborators can be QA teams supporting the team's activities, consumers of the team's APIs, or an entire Organization. On teams that don't require approval, Collaborators can be added automatically. On teams that require approval, an Admin must approve the addition of Collaborators to keep parts of the team private while others are shared.
Each team within an Organization has its own set of independent roles:
Team role | Capabilities |
---|---|
Team Manager (Team Super Admin) |
|
Team Member |
|
Collaborator |
|
Notes:
- Only a Team Member can create workspaces in the team.
- Sharing an element with a new user triggers the process of adding that user to the Team's user list.
- Any time a Team Member or Collaborator is removed from the Team's user list, they lose access to everything in the Team (until they're added back).
To configure your Organization Settings, select Organization in the Postman header, then select Organization Settings. The settings enable you to do the following:
To create an Organization Team, do the following:
Select Create Team.
Name your team. The team will be taggable in the mentions using @
, for example, @api-developers
.
Select Add Members. To be added, members need to be part of the organization.
Notes:
- If no Team Manager is assigned, the Organization Manager can continue to manage the Team membership.
- You can use Groups to assign Team membership, enabling control through an Identity Provider (IdP) and SCIM.
To create workspaces for an Organization Team, do the following:
If you're not continuing from the previous step, from the Home page, select Workspaces.
Select Create Workspace.
Select a blank workspace or a workspace template. Select Next.
Name the workspace.
Select the team for which to create a workspace. Otherwise, your team will be prepopulated.
Select Internal for workspace type. You can update the workspace visibility at any time. As a best practice, workspaces need to remain internal until all the work has been completed and approved.
Select Everyone in [TeamName] to allow all Team Members with access to the workspace, whether invited or shared, to edit the workspace elements. Collaborators will still have to be added to the workspace roles to enable their access. For stricter access, select Only you and invited people. If there's a specific need to open the workspaces to all people in the Organization, select Everyone in [OrgName].
Select Create.
After you create one or more workspaces, you can add workspace details, connect the workspace to a Slack or Teams channel, and post a workspace update announcing the workspace is ready for collaboration.
Postman recommends adding a useful workspace description and other details to help Organization Teams start collaborating.
To identify workspaces further, do the following:
Your teams can continue to edit workspace details as their workspaces, collections, and APIs evolve.
To learn more, see Edit workspace details.
To post a workspace update, do the following:
From the workspace, select Updates.
Select Post an Update.
Enter a title and a description of your update.
Select Announcement from the dropdown list.
(Optional) Add a summary describing the change.
If you've integrated Postman with Slack or Teams, you can post a team workspace update to a channel on one or both of those apps. Select Post Update.
If a social channel is already subscribed to workspace updates the checkbox next to Share on Slack (or Teams) on the bottom right of the post will be checked. If not, select
![]()
Connect in the workspace overview to subscribe to a channel. Ensure the box is checked to send notifications when someone posts a workspace update. To learn more, visit the Slack and Teams integrations pages, respectively.
Last modified: 2025/04/21