> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/getting-started/concepts/identity-lifecycle-management-idlcm.md).

# Identity Lifecycle Management (IdLCM)

Understand how Cerby automates identity provisioning and deprovisioning through IdLCM integrations and business hubs.

Managing who has access to what, across dozens of apps, is one of the most time-consuming and error-prone tasks in IT. Cerby's Identity Lifecycle Management (IdLCM) solution eliminates that burden by connecting your disconnected apps to your identity platform, so the same automated workflows that govern your core systems can now govern every app in your portfolio.

Together, business hubs and IdLCM integrations give you complete lifecycle coverage: from the apps your marketing team uses every day to the enterprise tools your engineering and operations teams depend on.

{% content-ref url="/pages/A60YJUwoMrenKszAy0wj" %}
[Business hubs](/getting-started/concepts/identity-lifecycle-management-idlcm/business-hubs.md)
{% endcontent-ref %}

{% content-ref url="/pages/JoLpEsQ3J5CxFctiHj9b" %}
[IdLCM integrations](/getting-started/concepts/identity-lifecycle-management-idlcm/idlcm-integrations.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.cerby.com/getting-started/concepts/identity-lifecycle-management-idlcm.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.