Defining roles

Certain team options are only available on Postman Team, Business, and Enterprise plans. To see which roles are available on your plan, go to your web dashboard.

In Postman you can assign roles and permissions to provide access control.

Contents

• Roles in Postman

  • Team roles
  • Workspace roles
  • API roles
  • Collection roles
• Managing roles and permissions
• Roles FAQ
• Next steps

Roles in Postman

As a team admin, you have the power to define Postman access at the team 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 personnel. Team members with the billing role can modify who else has billing roles at the team level.

Workspace admins can modify the admin and collaborator roles for the workspace. Editors of particular elements (APIs, collections, environments, monitors, and mock servers) can modify the editor and viewer role on the element.

With these roles, you and your teammates can manage access for each individual, or, if you are on a Postman Enterprise plan, for groups.

Team roles

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:

* On Postman Team and Free plans, any developer can change visibility of workspaces

** Enterprise and Business plans only

Workspace roles

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:

API roles

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:

Collection roles

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:

Managing roles and permissions

To manage team roles, see Managing roles.

Roles FAQ

• 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?
  You can remove a former colleague from your Postman team via your 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.

Next steps

Learn more about Working with your team.