> For the complete documentation index, see [llms.txt](https://documentation.efalia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.efalia.com/produit/acropolis/administration/valeurs-systeme/gestion-des-actions.md).

# Gestion des actions

## Blocage des modifications d'actions

Cette valeur permet d'activer le verrouillage pour l'ensemble de l'application de la zone « à effectuer le » lorsque l'utilisateur qui a créé l'action est différent de l'utilisateur courant.

| Code              | MACT |
| ----------------- | ---- |
| Valeurs possibles | VRAI |
| FAUX              |      |
| Valeur par défaut | FAUX |

## Visualisation des actions privées

Cette valeur permet de visualiser dans l'agenda les actions privées qui apparaissent en grisées.

| Code              | VISUAP |
| ----------------- | ------ |
| Valeurs possibles | VRAI   |
| FAUX              |        |
| Valeur par défaut | FAUX   |

## Afficher Lien Action Acteurs Utilisateur

Cette valeur permet d'afficher les liens actions acteurs de type demande DEMAND, AEFFEC, EFFECT.

| Code              | AFFLAAU |
| ----------------- | ------- |
| Valeurs possibles | VRAI    |
| FAUX              |         |
| Valeur par défaut | FAUX    |


---

# 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://documentation.efalia.com/produit/acropolis/administration/valeurs-systeme/gestion-des-actions.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.
