How to securely deploy Postman at scale, part 1: user management
Blog post from Postman
The blog post discusses the importance of securing Postman API Platform accounts and outlines best practices for managing access and user roles to prevent the leakage of sensitive information. It highlights the significance of assigning appropriate roles at the element, workspace, and team levels to ensure that users have suitable access, recommending a default Viewer role with Editors and Admins assigned as needed. The post also emphasizes the use of Postman’s version control workflows to maintain quality in shared collections and suggests implementing single sign-on (SSO) and SCIM for efficient user management. Additionally, it introduces Domain Capture as a feature to consolidate individual user accounts into a single, company-managed account to enhance collaboration and security. The post serves as Part 1 of a series aimed at guiding teams, regardless of size, in adopting robust security practices within the Postman platform.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.