SAML SSO
SoonNot shipped. Connector configuration and per-IdP setup guides exist; SAML sign-in itself does not.
- ✓Connector configuration stored per IdP — entity id, sign-on URL, certificate, metadata XML, attribute mappings
- ✓Setup guides for Okta, Entra ID, Google Workspace, OneLogin, JumpCloud, Ping and Auth0
- ✓A validation check that your metadata parses — it does not contact your IdP
- ✓No assertion endpoint, no JIT provisioning, no enforced SSO, no domain-based routing
What it is.
This is the page we most needed to correct. LexVio stores SAML connector configuration — your IdP entity id, sign-on URL, certificate, metadata XML and attribute mappings — with setup guidance for Okta, Entra ID, Google Workspace, OneLogin, JumpCloud, Ping and Auth0. That part is real and it looks convincing.
What is not there is SAML itself: no assertion consumer endpoint, no SAML library, nothing that receives or validates a SAMLResponse, and therefore no just-in-time provisioning and no way to disable password login in favour of the IdP. The connector test checks that your metadata parses; it does not contact your IdP. If SSO is a procurement requirement, treat this as not delivered.
Three steps.
End to end.
There is no SAML sign-in flow to configure your users into.
Storage for connector configuration and attribute mappings, with per-IdP setup guides.
The assertion endpoint, signature validation, JIT provisioning and SSO enforcement — that is, the feature.
What you get.
- ✓Connector configuration stored per IdP — entity id, sign-on URL, certificate, metadata XML, attribute mappings
- ✓Setup guides for Okta, Entra ID, Google Workspace, OneLogin, JumpCloud, Ping and Auth0
- ✓A validation check that your metadata parses — it does not contact your IdP
- ✓No assertion endpoint, no JIT provisioning, no enforced SSO, no domain-based routing
Quick answers.
No. There is nothing to receive the assertion. Password sign-in is the live authentication path.
No. There is an enforcement flag in the data model, and the login path does not read it. Do not rely on it as a control.
SCIM user provisioning is genuinely implemented and is independent of SAML — see the SCIM page, including its own plan note.
More in Team & Enterprise.
Not built. The organisation is the isolation boundary; matters are how work is grouped inside it.
Four seeded roles with per-capability view / add / edit / delete permissions, plus custom roles you define.
Shared editing sessions on a document, and a propose-review-merge flow for changes to it.
Group contracts, research, obligations, meetings and tasks by matter — with a timeline of everything that happened on it.