> For the complete documentation index, see [llms.txt](https://docs.aohwv.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aohwv.dev/core-concepts/lifecycle.md). # Lifecycle Most identity risk appears at transitions. A **lifecycle event** records a change in a person's state. Events are tracked at the identity level, not per account. There are four kinds. ## Joiner Fires when an identity is created: the first user or account links to a new person. Means a new person exists in the graph and may need access provisioned. ## Mover Fires when an identity changes in a way that affects access: new department, role change, different group membership. Recorded at the identity level even when the change came from one account. Movers are where excess access accumulates, because new access is granted but old access is rarely removed. ## Leaver Fires when all of an identity's login-capable users become disabled or staged for disablement. ## Reactivation Fires when a previously inactive identity becomes active again (a returning employee or contractor). Not a new joiner: the history is still there, and old access may still be attached and need review. ## Why transitions, not snapshots AOH Sync records the *transitions*, not just current state, for accountability. "This person left on this date and these accounts were still active" is only answerable if the leaving was an event, not an absence in the latest sync. Lifecycle events feed the [audit trail](/core-concepts/audit-and-compliance.md) and inform [posture](/core-concepts/posture-and-anomalies.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.aohwv.dev/core-concepts/lifecycle.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.