Collaborate with the Postman community using public workspaces
A public workspace can enhance a new user’s onboarding experience with your API. Inspire your existing users with new use cases and resources, increase your API’s discovery in Postman search results, and enable you to work publicly with partners. Anyone in the Postman community can access a public workspace.
Make your team profile public
Before other Postman users can work with your team in a public workspace, your team needs to have a public team profile. A public team profile encourages other users to collaborate with you in a public workspace, enables you to ask for contributions and gather feedback, and increases your API’s discovery in search results. A public team profile also appears on the Postman API Network.
Admins manage the team profile and other team settings.
To make your team profile public, do the following:
- Click your profile in the header, then select the name of your organization or team.
- Click Team profile.
- Select Make my team’s profile public to set the profile to public.
For information on how to create a public profile, see Edit your publisher team.
Create a public workspace
You can create a public workspace to share your workspace and its elements with the Postman community on the Postman API Network.
To avoid exposing secrets, such as API keys, use the Postman Secret Scanner to scan your public workspaces and detect any exposed secrets.
To create a public workspace, do the following:
- In the Postman header, select
Home >
Workspaces. You can also click
Workspaces in the sidebar on the Postman homepage.
- Click Create workspace in the upper right.
- Enter a unique name for your workspace. You can’t have two public workspaces with the same name.
- Select
Public as your workspace type.
- If you’re not a Team Admin, enter a note for the Community Manager to review, explaining why you want to make the workspace public. The Community Manager will review your request and either approve or reject it based on the information you provide.
- (Optional) Create the workspace with Postman AI. Describe your API and Postman AI generates collections, specifications, and environments to help you get started.
- Click Create Workspace.
Convert an existing workspace to a public workspace
As a Workspace Admin, you can convert an existing workspace to a public workspace. If you’re on a Postman Team or Enterprise plan, making a workspace public requires a Community Manager’s approval. Once a workspace is public, all elements in that workspace become publicly available on the Postman API Network.
Before you convert your workspace to a public workspace, make sure you aren’t exposing any secrets. You can give your API consumers a placeholder variable or vault secret (recommended). Learn how the Secret Scanner scans your public workspaces.
Postman sends in-app and email notifications to all workspace members when the workspace is made public. To view your in-app notifications, click the notification icon in the Postman header.
To convert a workspace to a public workspace, do the following:
- Open the workspace you want to make public.
- In the sidebar, select
> Workspace overview.
- Click the Settings tab.
- Under Workspace type, click Change.
- Select
Public.
- If you’re not a Team Admin, enter a note for the Community Manager to review, explaining why you want to make the workspace public. The Community Manager will review your request and either approve or reject it based on the information you provide.
- Click Save changes or Submit request.
If you’re submitting a request to make a workspace public, the Secret Scanner scans the workspace for exposed secrets. The workspace’s visibility is set to internal until it’s approved. While you’re waiting for the request to be reviewed, you can check the status of the secret scan or cancel the request from the workspace settings.
Feature collections in public workspaces
You can feature collections in a public workspace to give API consumers quick access to specific collections. On a public workspace’s Docs tab in the Featured collections section, click and select the collection you’d like to feature.
You can choose an environment for each featured collection you’d like to be active when it’s opened. The environment is active in the environment selector.
To remove a featured collection, hover over the collection and click .
Invite collaboration on a public workspace
An informative and inviting public workspace can help increase adoption of your APIs. To invite collaboration from other users on your public workspace, you must have:
- A complete public team profile.
- A complete workspace overview, including a name, summary, and description.
- Descriptive documentation for your APIs.
Signs of a public workspace that invites collaboration include:
- Active forks of your workspace — The number of people who fork your workspace and work on their forks shows strong collaborator engagement.
- People watching your workspace — The number of people who watch your workspace for activity can reflect interest from potential collaborators.
- Recent activity on the workspace — A workspace activity feed that shows ongoing work reassures potential collaborators that your team updates and maintains the workspace.
Share a public workspace
You can share a public workspace by giving collaborators its workspace URL directly.
To access a workspace’s URL, do the following:
- Open the workspace you want to share.
- In the sidebar, select
> Workspace overview.
- In the upper right of the workbench, click
Copy link to workspace.
When you share a workspace with Postman users who aren’t team members, its visibility must be public. If the workspace is an internal workspace, users who don’t have access won’t be able to open it.
Announce your workspace updates
Keep the watchers of your workspace and collection informed about any changes to your APIs. You can share updates across multiple collections and link to the specific request, collection, or folder that changed. These watchers get notified and can engage with these updates by commenting and reacting.
Post an update
You can post updates to keep your workspace watchers informed about changes to your APIs. Postman teams can connect up to 10 Slack channels to a single public workspace. Your API consumers can respond to a workspace update by adding a comment or reacting with an emoji response.
To post a workspace update, do the following:
- Open a workspace and click the Updates tab. If this is the first update, select Post an Update. Otherwise, you’ll see a Post an update field above other updates.
- Enter your update’s title and description.
- Select an Improvement, New Feature, Bug Fix, Breaking Change, or Announcement tag from the dropdown list.
- (Optional) Click Link a Resource to include links to collections, requests, and saved examples in your update. When you add links to collections or requests, the watchers of the collections, who may not be watching the workspace, are notified about the update alongside workspace watchers.
- Click Post Update. If you’ve integrated Postman with Slack, you can post a workspace update to a channel.
If a Slack channel is already subscribed to workspace updates, the checkbox next to Share on Slack on the bottom right of the post is checked. If not, click 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 integrations page.
Share workspace updates
To share a workspace update, do the following:
-
Click
.
-
You can choose from the following sharing options:
- Share via X — Share the update on X.
- Share via LinkedIn — Share the update on LinkedIn.
- Copy Link — Copy a link to the update that you can share anywhere.
- Post updates to Slack — If you have a Slack channel connected to the workspace, you can post the update to the channel.
Viewers in a public workspace (including those inside and outside the team that owns the public workspace) can subscribe to public workspace updates.
Edit or delete a workspace update
To edit or delete a workspace update, do the following:
- Open a workspace and click the Updates tab.
- Click
.
- Select Edit or Delete.
Manage a public workspace
When a user opens a public workspace, Postman displays an overview of its contents, activity, and members. The user interacts with the contents of the public workspace, including the collections, environments, and other elements. A team member with an Admin role on the workspace can manage the overview, elements in the workspace, and the members of the workspace.
Edit public workspace details
Users with an Admin role for a workspace can edit workspace details, including updating the workspace’s name, summary, description, and visibility. For more information, see Editing workspace details.
To improve your workspace’s visibility on the Postman API Network, ensure that your workspace’s name is unique and your workspace summary clearly describes its contents and purpose.
Move elements to a public workspace
You can move Postman elements from your internal workspace into a public workspace. Elements include collections, environments, mock servers, flows, and specifications. You must have an Admin or Editor role for the public workspace to move elements to it.
You can’t move elements from a public workspace to an internal workspace.
To move an existing element to a public workspace, do the following:
- Select
View more actions next to the element, then select Move.
- Select the public workspace to which you want to move the element, then select Move (Element).
The Postman element that you move to the public workspace no longer exists in the original workspace.
If there are monitors, mock servers, or integrations associated with the moved element, they remain in the original workspace.
Delete elements from a public workspace
You can delete Postman elements from a public workspace for which you have an Admin or Editor role.
- In the sidebar, click
View more actions next to the element, then select Delete.
- Click Delete to confirm your choice.
Learn more about deleting a collection and restoring a deleted collection.
Delete a public workspace
To delete a public workspace, you must change its visibility first. You must have an Admin role for a workspace to be able to delete it.
- On the workspace overview, click the Settings tab.
- Under Workspace type, select Change.
- Select Internal.
- Click Save changes.
- After you update its visibility, click Delete workspace.
- Enter the workspace name to confirm that you want to delete it, then click Delete workspace.
Manage public workspace users and roles
If you’re an Admin, you can manage collaborators and user roles in a public workspace:
- Invite team members, groups, and external users to collaborate in a public workspace. When they’re added to the public workspace, they’ll receive an email and in-app notification. To learn more about inviting users to work with you in your public workspace, see Sharing workspaces.
- Assign access to elements within a workspace. Workspace roles control access to elements. You can assign workspace roles to an individual user or to a user group. To learn more about assigning workspace roles or removing a user from a workspace, see Manage workspace roles.
Collaborate in another user’s public workspace
To collaborate with someone else in their public workspace, select Home >
Workspaces in the Postman header, then select the workspace you want to work in. You can also click
Workspaces in the sidebar on the Postman Home interface.
For collections, environments, and specifications, create a fork. To request to merge changes to collections and environments, create a pull request.
You can access public workspaces using the Postman Explore page’s Workspaces category. You can also access the public workspaces that you own or are a member of by clicking
Workspaces in the header.
The list of avatars in the Postman header shows you who’s active in your workspace. The list includes all active users with public profiles, and users who’ve chosen to remain anonymous by not enabling their public profile.
Viewers in a public workspace (including those inside and outside the team that owns the public workspace) can subscribe to public workspace updates.
Next steps
Once you start working collaboratively in a public workspace, users can fork collections and create pull requests.
- To learn more about version control in Postman, visit Version control for Postman elements.