Single Sign-On for MyPressable, Managed by Your Identity Provider
Many teams start with one shared MyPressable login. As teams grow, that login ends up with 10, 20, or 30 people on it, and no clear record of who still has access.
Single Sign-On connects MyPressable to the identity provider you already use, like Okta, Microsoft Entra ID, or Google Workspace. Each person signs in with their own work credentials.
SSO and SCIM provisioning are included on every Pressable plan.
Set It Up Yourself, and Switch Over When You’re Ready
Connect your identity provider: In Tools > Single Sign-On, copy the Entity ID and ACS URL into your identity provider, then paste back its metadata URL. Certificate changes are picked up automatically.
Verify your domain and test: Add a DNS TXT record, then run a test login. Until you enforce SSO, your team can try it with a Continue with single sign-on button.
Turn on enforcement: See who enforcement will cover, then enable it. Everyone on your verified domains signs in through your identity provider, and you can turn it off at any time.
Offboarding That Happens in Your Identity Provider
With SCIM provisioning, your identity provider keeps MyPressable in sync.
Why teams use Pressable Single Sign-On:
- One login per person: Everyone on your verified domain signs in with their own credentials instead of a shared password.
- Sign-in ends when someone leaves: Deactivate someone in your identity provider, and their SSO sign-in is blocked and their sessions end. With enforcement on, they can’t sign in at all.
- Your security policies apply: The MFA and sign-in rules you set in your identity provider apply to MyPressable.
- Setup your IT lead can own: Give them the Manage Single Sign-On permission, and they can handle setup without the account owner.
