> For the complete documentation index, see [llms.txt](https://athome-1.gitbook.io/athome-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://athome-1.gitbook.io/athome-docs/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](/athome-docs/assistance/tickets/ticketmanagement.md).

![The life cycle matrix of a ticket (standard interface)](https://2965217165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBk8u0TPogHtiUd7DaQyf%2Fuploads%2Fgit-blob-a6e0202feaef2e016123b8067e5da9499697c140%2Fticket_cycle_status.png?alt=media)

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://2965217165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBk8u0TPogHtiUd7DaQyf%2Fuploads%2Fgit-blob-c126822e3feffc87de716ddc71a27db6d65d232f%2Fticket_cycle_status.self_servicepng.png?alt=media)

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](/athome-docs/assistance/problems.md).

![The life cycle matrix of a problem](https://2965217165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBk8u0TPogHtiUd7DaQyf%2Fuploads%2Fgit-blob-23de1682df0da265f9d5a98bc2c1b6a7fa7e1dd5%2Fproblem_cycle_status.png?alt=media)

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](/athome-docs/assistance/changes.md).

![The life cycle matrix of a change](https://2965217165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBk8u0TPogHtiUd7DaQyf%2Fuploads%2Fgit-blob-5712fe19e79e0b95629fda9a3bdfb9de83d08c4c%2Fchange_cycle_status.png?alt=media)

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.