The Postman Collaboration Webinar

Postman offers all of its services and the majority of features to all users, regardless of plan type. To find your account's usage limits, please check out our feature matrix or your usage dashboard.

Postman's security policies are available here. Please reach out with any further questions or organization-specific inquiries.

At this time, a Postman account can only be a part of a single team.

Postman licenses are transferable between users and can be reassigned whenever you'd like. You can find more on team management in our docs.

Check out our docs on how to create workspaces.

See our docs on sharing workspaces.

Yes! In the app, you'll see an option to Invite your teammates. Upon inviting them, it will be automatically converted to a team workspace.

Newman is a command-line collection runner, so workspace navigation is beyond its scope. However, you can use Newman with the Postman API to retrieve workspace information.

Sharing a personal collection to a team workspace only changes the visibility of the collection—it does not create a copy of the collection.

Yes, all changes to shared collections are synced across workspaces. To get around this, you can create a copy of the collection and edit it first before editing the original collection.

Yes—to do this, share the collection, then remove it from the original workspace.

Yes—check out session variables.

You'll need to share the environment to your personal workspace in order for your variables to be resolved.

Global variables are associated with workspaces, so they'll resolve as long as the collection is within the correct workspace.

Ideally, you would create a private workspace for each vendor to keep them completely separate. Permissions would depend entirely on the level of control you'd like to provide the vendors. Please feel free to share your use case with us, so that we can work with you to find the right setup.

Postman doesn't prescribe a specific format for how you should configure your workspaces, collections and environments. The path you choose to take will depend on your team size and use case amongst other things. See this blog post for more information.

You will not be able to edit collections unless the original author grants you editing access. If you have a view-only role for a collection, you will need to request edit access.

A view-only user will be able to make certain edits to send a request, but will not be able to save those changes to the base collection. They can, however, create a fork and tag the collection admin in a comment to review said fork and merge it into the master collection.

View-only users can send team members with edit access a link to their merge page in the Postman Dashboard, or leave them a comment asking them to merge their fork.

We have a conflict management system.

Yes, you can add comments to any collection or request. Check out commenting on collections.

Pro and Enterprise plans come with a collection changelog that anyone with edit permissions can use to restore past versions.

Yep—check out our docs on viewing private documentation.

This is not currently possible.

We recommend Newman for this, learn more here.

Paid Postman teams can utilize our direct integration with Github. Learn more, here.

Nope—as of recently, anyone can publish to the API Network.

Featured APIs are curated by the Postman team—we look for well-documented APIs that clearly show users how to interact with them.

You can unshare your team profile, however that will also unpublish all of the collections associated with your team.