The Free plan is now a single-player plan for individual developers.
Individual users on the Free plan get a solid API workflow with core development, testing, mocks, Git integration, and built-in AI. Shared workspaces and collaboration are not included.
What does this mean for users who were part of a Free Team?
This change affects team members with full or limited access to Shared Workspaces. It concerns the team, not who created or owns the Shared Workspace or its elements (Collections, Environments).
Only one Admin will have full access to all Shared Workspaces; other team members will have read-only access.
If the team had only one Admin, that person kept the role. If there were multiple Admins, the selected Admin was chosen based on these criteria:
When a team becomes read-only, Postman automatically selects one admin to retain editing access. We choose the user with the highest-privilege role, and if multiple users qualify, we select the most recently active user.
If the wrong team member is set as Admin, contact the Postman Team at [email protected] to update it.
What does that experience look like in the platform?
Users see a different view based on their new role. Admins keep full access to the Shared Workspace and can perform all actions.
Read-only users can access Shared Workspaces but have limited actions within them.
An in-app banner will notify users of the change and include a link to the Team Settings screen showing user roles.
How to use collections from a read-only shared workspace?
Although direct access and sending requests to these Collections is limited, you can access them through the Admin. The Admin can share them with other Postman users, either by Export/Import or by connecting the Workspace to a remote git repo for others to access.
You can also use the Postman API to copy the Collection and place it in a new Individual Workspace where you have full control.
Here’s a guide outlining that flow: