> 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/connecteurs/verticaux/gestion-des-deliberations/configuration-open-delib.md).

# Configuration Open Delib

Configuration d'Open Delib pour le vertical Gestion des délibérations.

{% hint style="warning" %}
🚧 Cette page est en attente de rédaction par l'équipe produit Acropolis / Open Delib.
{% endhint %}

En résumé, Open Delib doit être configuré pour :

* déverser dans Efalia Doc les délibérations et arrêtés dont la gestion est terminée et les documents devenus non modifiables, en respectant le [plan de classement](/connecteurs/verticaux/gestion-des-deliberations.md#plan-de-classement) commun au vertical ;
* piloter, à la création de chaque dossier dans Efalia Doc, la valeur du [filtre d'accès Publiable / Non Publiable](/connecteurs/verticaux/gestion-des-deliberations/configuration-efalia-doc.md#filtre-dacces-publiable-non-publiable) selon que le document est destiné ou non à être exposé sur Efalia Portal.

Pour le détail de la configuration (paramétrage du connecteur côté Open Delib, mapping des types d'actes, etc.), contactez votre chef de projet Efalia.


---

# 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/connecteurs/verticaux/gestion-des-deliberations/configuration-open-delib.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.