> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/documentation/modules/administration/profiles/lifecyclematrix.md).

# Life cycle matrix

Each profile having its own life cycle matrix, it is possible to refine which profile will be able to do which action.

The life cycle matrix controls object status changes, which implies it can block some actions. If a status is not activated, it won't be present in the list of status of the object.

## Ticket life cycle matrix

See [Ticket management rules](/documentation/modules/assistance/tickets/ticketmanagement.md).

![The life cycle matrix of a ticket (standard interface)](https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FC0v6xyuwy4dyFEIml2Ks%2Fticket_cycle_status.png?alt=media\&token=9b9b6306-0df8-4985-9212-d15bb785d8fd)

In example above, a `New` ticket will never be put to `Waiting`, this status being not proposed in the ticket.

Furthermore, a requester will not have access to solution validation form, because a solved ticket for which solution has been approved becomes closed, which is not authorized by the example.

![The life cycle matrix of a ticket (simplified interface)](https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FTHJdiS2vQGnRm6hUkX7D%2Fticket_cycle_status.self_servicepng.png?alt=media\&token=f70792d3-fa0c-46f8-8620-e82e06601391)

For the simplified interface, ticket life cycle allows to define if user can close a ticket (solution approved) and if user can re-open it event if it is closed.

## Problem life cycle matrix

See [Ticket management rules](/documentation/modules/assistance/problems.md).

![The life cycle matrix of a problem](https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FvSIjZpm9fK2bjzF7CJMZ%2Fproblem_cycle_status.png?alt=media\&token=24c89864-fa95-407d-b66b-b1099ce116de)

In example above, a `New` problem will never be put directly to status `Solved`, this status being not proposed in the problem.

## Change life cycle matrix

See [Ticket management rules](/documentation/modules/assistance/changes.md).

![The life cycle matrix of a change](https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FlKHlLd0EhaENnVz3EsvL%2Fchange_cycle_status.png?alt=media\&token=cccccf03-c6e5-4cc1-9770-b72c7c3953d5)

In example above, a `New` change will never be `Accepted` before having its status put to `Evaluation` or `Validation`, this status being not proposed in the change.


---

# 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.glpi-project.org/documentation/modules/administration/profiles/lifecyclematrix.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.