For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Postman
PricingEnterprise
Contact SalesSign InSign Up for Free
HomeDocs
HomeDocs
      • Overview
      • Onboarding checklist
      • Roles and permissions
      • System service accounts
      • Free and Solo experience
      • Team migration
        • Intro to SSO
        • Configure SSO
        • Sign in to SSO
        • SSO and SCIM FAQs
        • Microsoft AD FS
        • Microsoft Entra ID
        • Custom SAML
        • Duo
        • Google Workspace
        • Okta
        • OneLogin
        • Ping Identity
      • Admin FAQs
Postman API Platform

Product

  • Postman Overview
  • Enterprise
  • Spec Hub
  • Flows
  • Agent Mode
  • API Catalog
  • Fern
  • Postman CLI
  • Integrations
  • Workspaces
  • Plans and pricing

API Network

  • App Security
  • Artificial Intelligence
  • Communication
  • Data Analytics
  • Database
  • Developer Productivity
  • DevOps
  • Ecommerce
  • eSignature
  • Financial Services
  • Payments
  • Travel

Resources

  • Postman Docs
  • Academy
  • Community
  • Templates
  • Intergalactic
  • Videos
  • MCP Servers

Legal and Security

  • Legal Terms Hub
  • Terms of Service
  • Postman Product Terms
  • Security
  • Website Terms of Use

Company

  • About
  • Careers and culture
  • Contact us
  • Partner program
  • Customer stories
  • Student programs
  • Press and media
Twitter iconLinkedIn iconGithub iconYouTube iconInstagram iconDiscord icon
Download Postman
Privacy Policy

© 2026 Postman, Inc.

On this page
  • What are the advantages of SSO?
  • Prerequisites for SSO with Postman
  • Supported IdPs
  • SSO setup for SAML 2.0 compliant IdPs
  • Learn more
Administer PostmanSingle Sign-On (SSO)

Intro to SSO

||View as Markdown|
Was this page helpful?
Previous

View reports about detected, unresolved, and resolved secrets

Next

Configure SSO

Built with

This feature is available on Postman Enterprise plans and Team plans with the Simple Security add-on. For more information, see the pricing page.

Single sign-on (SSO) services enable you to manage your organization or team’s identity across all the SaaS products that you use.

With an SSO service, a user can access multiple applications using one set of credentials (for example, an email address and password). The SSO service authenticates the user once for all the applications the user has been given rights to and eliminates further prompts when the user switches applications during the same session.

An example of SSO is Google’s sign-in implementation for products like Gmail, YouTube, and Google Drive. Any user who is signed in to one of Google’s products is automatically signed in to their other products as well.

What are the advantages of SSO?

  • Removes the need for users to remember and manage multiple passwords.
  • Simplifies users’ experience by enabling them to sign in at a single access point and work seamlessly across multiple applications.
  • Increases productivity by reducing the password-related support emails.
  • Reduces phishing attempts that try to trick users into giving away sensitive information.

Prerequisites for SSO with Postman

  • Team’s identity provider (IdP) must support the SAML 2.0 standard.

Supported IdPs

  • Microsoft AD FS
  • Microsoft Entra ID
  • Custom SAML
  • Duo
  • Google Workspace
  • Okta
  • OneLogin
  • Ping Identity

SSO setup for SAML 2.0 compliant IdPs

Most SAML 2.0 compliant identity providers require the same information about the service provider for setup (Postman is the service provider). These values are specific to a Postman organization or team and are available while configuring SSO.

Note
  • While configuring your IdP, set your users’ email addresses in SAML attributes and claims. Postman expects to receive an email address from your IdP to identify each user.
  • If you configure SSO, Postman Password, Google OAuth 2.0, and GitHub authentication methods remain enabled for your organization or team. You can turn off these authentication methods to allow your members to sign in using SSO only.

Learn more

To learn more about SSO and SCIM, see the following:

  • Sign in to SSO - How to sign in and use SSO when it’s enabled for your organization or team.
  • Configure SSO - How Admins can enable and configure SSO for organization or team users.
  • SCIM (System for Cross-domain Identity Management) provisioning - How Admins can use SCIM to automate user provisioning and de-provisioning for an organization or team.
  • SSO and SCIM FAQs - Frequently asked questions on configuring SSO and SCIM.