- 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
In Postman you can assign roles and permissions to provide access control.
- Managing roles and permissions
- Roles FAQ
- Next steps
As a team admin, you have the power to define Postman access at the team, workspace, collection, and API level. You can utilize Postman's role-based access control system to limit visibility of team resources, define your development workflow, and provide access to administrative and billing personnel.
You can assign one or more role types to team members: Admin, Billing, and Developer. If you are on a Postman Business or Enterprise plan, you will also have the option of assigning a Community Manager.
- Admin: manage team members and team settings
- Billing: manage team plan and payments
- Developer: access team resources and workspaces
- Community Manager: manage public visibility of workspaces and team profile (Business and Enterprise plans only)
Each user must have at least one role attached to them, and can hold multiple roles simultaneously.
Team roles provide high-level access control:
|Manage team Admins and Developers||✔|
|Manage custom domains||✔|
|View audit logs||✔||✔|
|View usage data||✔||✔||✔||✔|
|Manage Billing members||✔|
|View shared APIs, collections, environments, mock servers and monitors||✔||✔|
|View and create team workspaces||✔||✔|
|Change visibility of workspaces to team or public||✔*||✔|
|Approve requests to change workspace visibility**||✔|
|Enable public team profile||✔||✔|
* On Postman Team and Free plans, any developer can change visibility of workspaces
** Enterprise and Business plans only
You can assign two role types in Postman workspaces: Admin and Collaborator.
- Admin: manage workspace details and members
- Collaborator: work on team resources in a workspace
The following roles control access at a workspace level:
|Edit workspace details||✔|
|Join and leave workspaces||✔||✔|
|Manage workspace roles||✔|
|Manage workspace visibility||✔|
|Add and remove APIs, collections, and environments||✔||✔|
|Add monitors and mock servers||✔||✔|
You can assign two role types in Postman APIs: Editor and Viewer.
- Editor: edit APIs directly
- Viewer: view, fork, and export APIs
The following roles control access at an API level:
|Edit and delete APIs||✔|
|Manage roles on APIs||✔|
|Comment on APIs||✔||✔|
|Create new API versions||✔|
|Generate collections from the schema||✔||✔|
|View reports for APIs||✔||✔|
|Add and remove API environments||✔||✔|
|Add and remove API documentation||✔||✔|
|Add and remove API test suites, integration tests, and contract tests||✔||✔|
|Add and remove API monitors||✔||✔|
|Add and remove API mock servers||✔||✔|
You can assign two role types in Postman collections: Editor and Viewer.
- Editor: edit collections directly
- Viewer: view, fork, and export collections
The following roles control access at a collection level:
|Edit and delete collections||✔|
|Manage roles on collections||✔|
|Merge forks on collections||✔|
|Publish collection documentation and add to API Network||✔|
|Share collections to a different workspace||✔||✔|
|Tag and restore collection versions||✔|
|Add, edit, and delete mock servers||✔|
|Add, edit, and delete monitors||✔|
To manage team roles, see Managing roles.
- Our only team member with billing/admin permissions left - what can I do?
Contact us via our Support Center for assistance.
- I'm an admin, why can't I assign the billing role?
Billing roles can only be granted by a fellow team member with a billing role. If this is not possible, contact us via our Support Center for assistance.
- Is there a "Super Admin" role?
A "Super Admin" role is being considered for development. You can track progress and upvote this issue on GitHub to show your support.
- Our colleague left the organization, how can we access their collections?
Remove the former colleague from your Postman team in the web dashboard. When a collection owner is removed from your team, ownership of their shared collections is transferred to fellow team members and these collections will continue to exist in your Postman team.
- What are "support" roles?
A support-only account is one that holds an admin and/or billing role, but is not a developer. Teams can have up to two support-only accounts.
Learn more about Working with your team.