--- title: "Pressable Single Sign-On: Team Access, Managed by Your Identity Provider" url: "https://pressable.com/blog/pressable-single-sign-on-team-access-managed-by-your-identity-provider/" published: 2026-10-05 modified: 2026-10-05 author: Suzanne Kolpakov featured_image: "https://i0.wp.com/pressable.com/wp-content/uploads/2026/10/pressable-sso.png?fit=2048%2C1152&ssl=1" categories: - name: Announcements url: "https://pressable.com/blog/category/announcements/?format=md" --- For a lot of teams, MyPressable access started with one shared login. Then the team grew. Now 10, 20, sometimes 30 or more people use the same account, and nobody can say for sure who changed what, or who still has the password after they’ve left. **Pressable Single Sign-On fixes that.** ![](https://i0.wp.com/pressable.com/wp-content/uploads/2026/10/image-3.png?resize=1024%2C532&ssl=1)SSO connects MyPressable to your company’s identity provider. Every person signs in with their own work credentials, and your IT team manages their access alongside the rest of your company’s apps. ### **What Is Single Sign-On?** Single sign-on lets people use one set of company credentials to sign in to many apps. Your identity provider, such as Okta, Microsoft Entra ID, or Google Workspace, confirms who they are, and the app lets them in. With Pressable SSO, MyPressable becomes one of those apps. Your IT team adds people, removes them, and sets sign-in policies like multi-factor authentication in your identity provider, and those rules carry over to MyPressable. ### **What This Looks Like in Practice** ![](https://i0.wp.com/pressable.com/wp-content/uploads/2026/10/image-4.png?resize=1024%2C800&ssl=1)**When someone leaves the company** Your IT team deactivates them in your identity provider, the same way they would for email or Slack. With SCIM connected and enforcement on, they can no longer sign in to MyPressable, and their active sessions and API access end. There’s no shared password to change. **When a new developer joins** Add them in your identity provider, and SCIM creates their MyPressable account. An account owner grants access to the right sites through collaborator roles, and the new developer signs in with their work credentials. **When your whole team still shares one login** Verify your domain, run a test login, and turn on enforcement. Everyone on your domain now signs in through your identity provider with their own credentials, and passwords, passkeys, and other login options stop working for them. **When your security team reviews Pressable as a vendor** Questions about access control and offboarding have clear answers: SSO enforcement through your identity provider, and automatic deprovisioning with SCIM. **When your IT lead should own setup** The account owner gives them the Manage Single Sign-On permission, and they configure everything from Tools > Single Sign-On. The owner never has to touch the SAML settings. ### **What You Can Do Today** Pressable Single Sign-On includes: - Sign-in through SAML identity providers, including Okta, Microsoft Entra ID, Google Workspace, and Auth0. - Self-service setup using your identity provider’s metadata URL. - Email domain verification with a DNS TXT record. - A test login before anyone is switched over. - A view of who enforcement will cover, including collaborators outside your verified domains. - SSO enforcement for everyone on your verified domain. - Automatic provisioning and deprovisioning with SCIM. - Automatic pickup of identity provider certificate changes, with an email before a certificate expires. - A Manage Single Sign-On permission that owners and Account Administrators can give to a collaborator. ### **Built to Roll Out Safely** Setup and enforcement are separate steps, so you can check everything before anyone’s login changes. Until you enforce SSO, people on your domain see a Continue with single sign-on button next to the password field, so your team can try it first. When you’re ready, review who enforcement will cover and turn it on. You can turn it off again from the same page, and if your identity provider ever goes down, Pressable support can turn enforcement off for you. ### **Who It’s For** **Agencies** Give every developer and project manager their own login, and cut off their sign-in the day someone moves on. **Growing businesses and SaaS teams** Bring MyPressable under the same identity policies as the rest of your company’s tools, and answer yes when access control comes up in security reviews. **IT and security teams** Manage MyPressable access in your identity provider, and apply the MFA policies you already have. ### **Get Started** In MyPressable, go to **Tools > Single Sign-On** to connect your identity provider and run your first test login. **The [SSO setup guide](https://pressable.com/pressable-sso-guide/)** covers each step, with notes for Okta, Microsoft Entra ID, Google Workspace, and Auth0. For more details, visit our [Knowledge Base](https://pressable.com/knowledgebase/).