> For the complete documentation index, see [llms.txt](https://docs.mifos.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mifos.org/mifosx/user-manual/for-administrators-mifos-x-platform/clients-groups-and-centers/manage-clients/client-life-cycle-statuses.md).

# Client Life Cycle Statuses

This page details the Client Life Cycle Statuses and the transitions between the various statuses.

![](https://mifosforge.jira.com/wiki/download/thumbnails/89718816/client%20life%20cycle%20state%20digram.jpg?version=1\&modificationDate=1427539171834\&cacheVersion=1\&api=v2\&width=645)

| Action              | State                |
| ------------------- | -------------------- |
| Create client       | Pending for approval |
| Activate            | Active               |
| Close               | Closed               |
| Reject              | Rejected             |
| Withdrawn by client | Withdrawn            |
| Delete              | Deleted              |
| Reactivate          | Active               |

&#x20;On creating a new client, it moves into the  "Pending for approval" state. From the approval state, it can undergo the following transitions:

* On clicking on "Activate", the client gets "Active".\
  **OR**
* On clicking on "Close", the client gets "Closed".\
  **OR**
* On clicking on "Reject", the client gets "Rejected".\
  **OR**
* On clicking on "Withdrawn by client", the client gets "Withdrawn".\
  **OR**
* On clicking on "Delete" the client gets "Deleted". Once a client gets deleted, it won't show up anywhere in Mifos X.<br>
* If the client is in the "Closed" state, it can be "Reactivated" to make it "Active".
* If the client is in the following states: Rejected/Withdrawn/Deleted, it cannot be Activated again.&#x20;

**NOTE:** For the actions mentioned below, we need to update reasons as mentioned below in the Code Values (for more information, navigate to **Admin** >> **System** >> **Code**) :&#x20;

| Action   | Reason                   |
| -------- | ------------------------ |
| Close    | Client closure reason    |
| Withdraw | Client withdrawal reason |
| Reject   | Client Rejection reason  |

{% hint style="info" %}
Link for Reference: [Manage Clients](/mifosx/user-manual/for-administrators-mifos-x-platform/clients-groups-and-centers/manage-clients.md)
{% endhint %}

Related articles

* Page:[Loan with term vary based on loan cycle](/mifosx/user-manual/for-operational-users-mifos-x-web-app/accounts-and-transactions/loan-accounts/loan-with-term-vary-based-on-loan-cycle.md)
* Page:[Client Life Cycle Statuses](/mifosx/user-manual/for-administrators-mifos-x-platform/clients-groups-and-centers/manage-clients/client-life-cycle-statuses.md)
* Page:[Client Impact Portal User Guide](https://mifosforge.jira.com/wiki/spaces/docs/pages/76873819/Client+Impact+Portal+User+Guide)
* Page:[Search & View Client, Group, Account Details](https://mifosforge.jira.com/wiki/spaces/docs/pages/76873791)
* Page:[Using REST client for passing api requests](https://mifosforge.jira.com/wiki/spaces/docs/pages/112295941/Using+REST+client+for+passing+api+requests)


---

# 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.mifos.org/mifosx/user-manual/for-administrators-mifos-x-platform/clients-groups-and-centers/manage-clients/client-life-cycle-statuses.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.
