Docs with SSO, SCIM, an audit log and self-hosting.

Your team signs in with your identity provider, readers can too, security sees who changed what, and you can run Workover on your own servers.

Many teams, one set of rules.

Large companies publish docs from many teams at once. Each team needs its own review, readers need the right access, and security needs to see who changed what.

The controls a security review asks for.

  • SSO and SCIM

    SAML or OIDC single sign-on on your verified domains. SCIM provisioning, and removing someone revokes their access but keeps what they wrote.

  • Audit log

    Who did what and when, filtered by person or action and exported to CSV. On every plan.

  • Data controls

    Set how long trash, audit entries and sign-in sessions are kept, and export the whole workspace.

  • Self-hosting

    Run Workover Enterprise on your own infrastructure with Docker Compose. The license check is local and never phones home.

The right docs for each reader.

Readers sign in with your identity provider, or through your own app. Keep some pages public and the rest for signed-in readers, and show each customer the pages for their plan.

  • OIDC with Okta, Entra and others, or a JWT handoff from your app.
  • Page conditions and “Visible to” blocks on reader claims.
  • Site analytics in your own tools through the analytics API.

Questions

On Amazon Web Services (AWS) in the United Kingdom. Security

Talk to us about your docs.

We will walk through single sign-on, SCIM, reader sign-in and self-hosting with your team.