If you're just getting started using Postman within your organization, you can carry out a few preparation steps to set your team up for success.
Postman is available as a stand-alone app for Windows, Mac, and Linux, and can also be accessed via the web with a desktop agent. Make sure everyone who would like to use Postman has the latest version by downloading it from the Postman website. You may want to contact your IT team to establish what the procedure is for adding a new piece of software. This varies from organization to organization, however, the following points are common:
- Your IT team may need to add an exception to device policy allowing for Postman to be installed on employee workstations. Provide a Postman download link to the IT team to help establish this exception.
- If your organization's network connection is facilitated via a proxy, you may need to configure Postman appropriately. Retrieve proxy connection details from your IT team and setup within Postman.
It is recommended that your IT team whitelist Postman’s domains to ensure Postman data is synced with the cloud and all functionality works as expected. By default, WebSocket connections use the same ports as HTTP (80) and HTTPS (443). Ensure your network firewall allows WebSocket connections for Postman's services by whitelisting the following domains:
- Depending on your plan you may be able to obtain static IP addresses for Postman Monitors. Your IT team should whitelist these static IPs for monitoring. See Running Postman monitors using static IPs for details on how to obtain and configure static IP addresses for monitoring.
- Update your team settings. See Team Settings for more info.
- If your Postman plan includes single-sign-on (SSO) you may need help from your IT team to configure it. See Configuring SSO for a team for instructions on integrating with specific identity providers.
Depending on the size of your team you can send invites to your team now or Check Your Setup with a few volunteers before you rollout Postman to your entre organization.
Before you kick-off in full, it’s best to check in on the workings of Postman within your organization and ensure everything works as expected. If you do not have access to Postman and a Postman account, find a team member who does to help you test the configuration. Depending on your organization's IT policy you may need to make requests of your IT team in order to get up and running as well.
Ensure you are connected to your organization's network and test the following:
- Can you execute a request to
- Can you execute a request to one of your internal/private APIs?
- Save a request inside a Collection. Visit
go.postman.co, has your collection and request synced with Postman’s cloud?
Repeat these checks on a colleague’s workstation. If everything worked, your workstations and network are ready to support Postman! Else, if you experienced a hiccup, contact Postman support and please read on.
Team discovery makes Postman’s collaboration features more discoverable to users, and allows your team participation to scale up along with your successful API projects. When team discovery is enabled, users in your organization can see teams to join when they access their Postman accounts. Anyone signing in with a company email address is presented with available teams and can make a request to join each one. Administrators will receive a notification and can approve or deny access from there. See Team Discovery for more info.
If you have any questions or run into any issues setting up Postman for your team be sure and check to see if the question has already been answered by the Postman Community. You can also find a number of support resources on the support page.
Check out Security and Compliance: A Shared Responsibility Model for important security considerations.
Make sure to configure SSO if you are subscribed to the Business or Enterprise plan.
Finally, head over to Managing Your Team to learn about managing roles, inviting to workspaces, and how to adjust your team size.