Sign your team in with the identity provider you already run
SAML-based single sign-on lets everyone reach Manifestly through your own identity provider — no separate passwords to manage. Works with any SAML 2.0 IdP, from Okta and Microsoft Entra ID to OneLogin, Auth0, and Google.
Available on the Enterprise plan. See pricing · About Enterprise
Welcome to Acme on Manifestly
Your organization uses single sign-on.
Redirects to your identity provider
One front door, not another password
Every extra login is another credential to reset, another account to remember to switch off when someone leaves. Point Manifestly at the identity provider your organization already trusts and access follows the rules you already enforce.
- A separate credential for every tool
- Offboarding means chasing down each app
- Your security policy stops at the login box
- People sign in through your IdP
- Remove access in one place at offboarding
- MFA and access policies carry straight over
Live in three steps
Connect your identity provider
In your account's SSO settings, paste your IdP's sign-in URL, entity ID, and signing certificate. Manifestly hands back the assertion consumer and metadata URLs to register on the IdP side.
Test with your custom URL
Every account gets its own branded sign-in address. Run a real login through it end to end and confirm your team lands in Manifestly before you change anything else.
Make SSO required
Flip the required switch and every sign-in now goes through your identity provider — passwords and other methods are turned off for the whole account.
Connect any SAML 2.0 identity provider
Setup is a straight exchange of standard SAML values — no custom integration to build. You supply three details from your IdP; Manifestly supplies the service-provider endpoints to register on the other side. If your provider speaks SAML 2.0, it works.
- HTTP-POST assertion consumer binding with a transient NameID.
- Signing verified against your certificate's SHA-1 fingerprint.
- Only an admin can view or change your account's SSO configuration.
Provision users straight from your directory
SAML answers who is signing in; SCIM answers who belongs here. Included with SSO, SCIM lets your identity provider create Manifestly users the moment someone is assigned the app, and remove their access the moment they're unassigned — the two events that matter most for every new hire and every departure.
- Assign the app and a Manifestly user is created and added to your designated provisioning department.
- Unassign or offboard and their access is removed — the same path as an admin removing a user by hand.
- Authenticated with a Manifestly API key as a bearer token, scoped to your account.
# Your IdP provisions a new hire into Manifestly
POST /scim_v2/Users
Authorization: Bearer <api-key>
{
"userName": "dana@acme.co",
"name": { "givenName": "Dana", "familyName": "Ruiz" },
"emails": [{ "type": "work", "value": "dana@acme.co" }],
"active": true
}
# Offboarding sets active:false and removes their accessTurn it on when you're ready — not before
Enforcing SSO is a single switch, and you control the timing. Leave it optional while you validate the connection through your custom URL, then require it to lock the whole account to your identity provider. Because it's decisive, Manifestly tells you plainly: once SSO is required, you and your users can only sign in through your IdP.
- Test end to end on your branded URL before you enforce anything.
- When required, password and other sign-in methods are switched off account-wide.
- Users are matched by their email address, so identities line up with your directory.
Access that follows your policy
- Your IdP handles the actual authentication — MFA, conditional access, and device policy all apply before Manifestly ever sees the user.
- Identities are keyed to email, so people map cleanly to the accounts they already belong to.
- Deprovision in one place: removing someone in your directory removes their Manifestly access through SCIM.
- Required mode leaves a single, auditable way in — your identity provider.
SAML SSO, answered
Other Features
Govern, secure & prove it
SSO, granular permissions, and a complete audit trail — the controls enterprise teams need to run their work and prove how it was done.
Workflow Customization
Shape exactly how each workflow behaves — logic, data, timing, and documentation.
Assign and Automate
Get the right work to the right people, on schedule — automatically.
Track Progress and Reporting
See what's done, what's late, and what's coming — across every run.
Communicate
Keep the conversation — and a permanent record of who did what, and when — in one place.
Trusted by organizations big and small for their recurring workflows
Authenticate Your Team Using SAML SSO
With Manifestly, your team will Never Miss a Thing.