> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/human-access-and-agent-access/user-lifecycle.md).

# User Lifecycle

Cakewalk follows your company's HRIS through every stage of employment. Each lifecycle event lands in both modules of the platform: Human Access moves the person's app access, and Agent Access evaluates their Agents against the change.

### 📖 Key Concepts

* **Joiner**: a new hire synced from the HRIS triggers onboarding and receives the Apps their groups grant by default.
* **Mover**: a role, team or location change updates the attributes both modules read.
* **Leaver**: offboarding removes app access, Agent Access and the Connections (the apps their Agents connected to) that came with it.

:bulb: *Why this matters*: Agents act with their person's access. A lifecycle event that changes what a person may do also changes what their Agents may do, without anyone reconfiguring an Agent.

***

### 🚪 Joining

1. The new hire flows into Cakewalk on HRIS sync, with name, email, manager, department, title and location.
2. Onboarding grants the Apps the person's groups carry by default, by hand or through Agent Cake, Cakewalk's AI provisioning agent.
3. If their groups carry Agent Access by default, they hold it from day one and can connect their first Agent.

***

### 🔁 Moving

A role, team or location change updates the person's attributes, and both modules respond:

* **Human Access**: group memberships shift, which can add or remove the Apps those groups grant and flag access that no longer fits the new role.
* **Agent Access**: [Policies](https://www.cakewalk.security/docs/ai-agent-access/concepts/policies) (the rules that decide each agent action) evaluate department, title, team and location on every action, so the same HRIS change that moves someone's app access also changes what their Agents may do. The person changes departments; their Agents follow at their next action.

***

### 🚫 Leaving

Offboarding runs through Human Access and covers everything the person held:

* App seats are removed, with tasks created for anything that needs a human step.
* Their Agent Access is removed and the credentials behind their Connections are deleted. An Agent cannot reconnect or start a new session after that.
* An Agent still mid-session can keep working on its existing sign-in for a short time, at most 8 hours from when that sign-in was issued.

{% hint style="info" %}
Offboarded Users lose their Agent access automatically: nobody has to remember the Agents when closing out a departure.
{% endhint %}

***

### 📚 Related

* [How They Connect](/docs/human-access-and-agent-access/how-human-access-and-agent-access-connect.md)
* [HRIS and IdP](/docs/connections-and-integrations/hris-and-idp.md)
* [Joiner Mover Leaver in Human Access](https://www.cakewalk.security/docs/human-access/how-to-guides/users-and-groups/joiner-mover-leaver-jml)


---

# 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://www.cakewalk.security/docs/human-access-and-agent-access/user-lifecycle.md?ask=<question>&goal=<endgoal>
```

`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.