User lifecycle
The user lifecycle is the full arc of a person’s access: joining, changing roles, and leaving. Managing it well is a security discipline — most access risk comes from accounts that outlive the person’s need for them.
Provisioning
Section titled “Provisioning”Bringing someone in: an invite (or an automated sync) creates their account with the right role from the start. See Users & invitations. The goal is that people get exactly the access their job needs on day one, and no more.
Deprovisioning and deactivation
Section titled “Deprovisioning and deactivation”The other end matters just as much. When someone leaves or changes roles, an admin deactivates or adjusts their account so access ends cleanly. Deactivating a user cuts off their ability to sign in and act, while preserving the record of what they did for audit purposes. Leaving old accounts active is one of the most common — and most avoidable — enterprise security gaps.
Automating it (SCIM)
Section titled “Automating it (SCIM)”At scale, doing this by hand doesn’t hold up. SCIM is a standard that syncs users automatically from your identity provider: provision someone in your IdP and they appear in Rival; deactivate them there and their Rival access ends — no manual step. [VERIFY: confirm SCIM/automated provisioning is supported.]
Why it matters
Section titled “Why it matters”Access that matches employment, automatically, is the difference between a system your security team trusts and one they worry about. It’s also what makes audits painless: there are no mystery accounts to explain.
A quick example
Section titled “A quick example”A company syncs Rival with their identity provider via SCIM. When an employee transfers from Support to Sales, their team and permissions update automatically; when a contractor’s engagement ends, their access disappears the moment IT offboards them — without an admin ever touching Rival.