Renttix Single Sign-On

How it connects

Renttix supports enterprise single sign-on through two independent brokers, Clerk and WorkOS, which between them front the SAML and OIDC identity providers businesses actually use. Your users authenticate against your identity provider, and Renttix verifies the resulting token against the broker's published signing keys before establishing a session. That verification step is the security boundary. Renttix does not accept an assertion because it looks right — it validates the signature against the provider's key set, so a forged or expired token is rejected rather than trusted.

Why it matters

The security problem in most hire businesses is not passwords being guessed. It is leavers keeping access. Staff turnover in the industry is real, and when someone leaves, their accounts across a dozen systems are closed in whatever order somebody remembers. The rental system holds customer data, pricing and financial records, and it is rarely first on that list. Single sign-on collapses that to one action. Disabling someone in your identity provider ends their Renttix access at the same moment, because Renttix never held their password to begin with. It also removes the shared-login habit that grows in busy depots, since signing in with a personal company identity is easier than remembering a shared one — and that makes the audit trail mean something.

Single sign-on covers office and management users of the Renttix web application. Field staff sign in to the Renttix Field app separately with their own credentials, since drivers and engineers are frequently not part of a corporate directory — and their access is governed by the workforce seat and permission model instead.