Introduction
An essential part of working together on a project is efficiency. We all want smooth working between the members of our team. To do this, we need to assign members roles, so they know their part. It makes the members clear of their parts and their allowance in a team. However, we know that Postman has multiple parts where a different contributing method is needed. Let it be teams, workspaces, APIs or environments. We have other ways to give control over all sorts of takes. In Postman, we have all sets of combinations of assigned roles. In this article, we will talk about defining roles in Postman.

Roles in Postman
In Postman, access to team members is given according to needs. Following this, we can assign roles to the members. We will read below about the options available to us on giving roles.
Team Roles
We may define Postman access at the team level with the Admin role. To do this, we have Postman's role-based access control system. We can use it to specify team resource visibility, limit our development workflow, and grant administrative and billing people access. Each team member must have at least one role and may hold numerous roles at the same time.

We can give team members one or more role types based on the functions they need:
Super Admin
The Super Admin manages all team parts, such as team settings, members, roles, and resources in public, team, or private workspaces. This role lets team members do anything that the Admin, Billing, API Network Manager, Community Manager, and Developer roles can do. We can get them in Enterprise plans only.
Admin
An Admin controls the settings and members of the team.
Billing
The one here oversees team finances and plans. A Super Admin, a teammate in a billing job, or an Admin welcoming a new team member can all grant billing roles. Get in touch with the Support Center if doing so is not feasible.
Developer
Access to all workspaces and team resources is available to developers.
Community Manager
The Community Manager Controls how public workspaces and team profiles are displayed. We can get them in the Professional and Enterprise plan only.
API Network Manager
The Private API Network gets managed by an API Network Manager, who also approves or rejects requests to add APIs. A Super Admin or another team member with the API Network Manager role can give this role to a user. We can get them in Enterprise plans only.
Workspace Roles
Workspaces let us arrange our Postman projects and communicate with coworkers. We can combine our projects. The workspace will be the sole authoritative source for all associated APIs, collections, environments, mocks, monitors, and other connected elements.
Admin - The Admin controls workplace settings and resources.
Editor - The Editor is the creator and editor of workspace resources
Viewer- The Viewer can view, fork, and export resources in the workspace.

Element-based roles
Team members can be given roles determining their access to Postman collections, APIs, mock servers, and monitors at the element level.
Collection Roles
In Postman collections, we can assign the Editor and Viewer roles.
We can organise our API development and testing operations using Postman Collections. Additionally, we may create collections from API schemas, share them, and do more.
Editor - The Editor has direct access to editing collections.
Viewer- The Viewer can view, fork, and export collections.

API Roles
Editor and Viewer are the two roles that can get assigned in Postman APIs. Thanks to the Postman API, data stored in our Postman account may be easily accessed programmatically.
Editor - The Editor has direct API editing capacity.
Viewer - The Viewer can check and export APIs.

Environment Roles
Editor and Viewer are the roles that can be given in Postman environments. A set of variables called an environment is available in Postman requests. When working in a team, environments can be used to control who has access to shared Postman data and group-related sets of values.
Editor -The editor has Editing and environment management capabilities
Viewer - The Viewer is Capable of viewing and using environments.

Mock Server Roles
Editor and Viewer are the two roles that we can assign in Postman mock servers. We can develop or test against an API before it is ready for production by utilising mock servers, which simulate an API by returning predetermined data or without using production data.
Editor - The Editor can manage mock servers and also edit them.
Viewer - The Viewer can see mock servers and related metadata.

Monitor Roles
Editor and Viewer are the roles that can be given in Postman monitors. Thanks to Postman Monitors, we have constant access to information on the functionality and health of the APIs.
Editor -An Editor can View and tracks metrics, jobs, runs, and metadata. The monitor can be run, updated, deleted, paused, and resumed.
Viewer - A viewer can view the metrics, jobs, metadata and runs related to monitoring.
