> 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-efalia-portal.md).

# Configuration Efalia Portal

Fichier properties et configuration des menus IHM pour la publication des délibérations sur Efalia Portal.

Configurer Efalia Portal nécessite deux étapes distinctes.

{% stepper %}
{% step %}

## Fichier properties

Renseigner les propriétés suivantes :

```
docApi.armoires = xxxx    // Identifiant externe de l'armoire contenant les dossiers
docApi.portal.user = xxxx // Identifiant du compte technique
docApi.portal.password = xxxx // Mot de passe du compte technique
```

Le compte technique référencé ici est celui créé côté Efalia Doc — voir [Configuration Efalia Doc](/connecteurs/verticaux/gestion-des-deliberations/configuration-efalia-doc.md#compte-technique-efalia-portal).
{% endstep %}

{% step %}

## Configuration XML des menus

Modifier la configuration XML pour faire apparaître le ou les menus de type Acte avec séance (Délibérations) ou Acte sans séance (Arrêtés), au niveau du nœud `Portal > IHM > MENU` :

```xml
<ihm>
	<menu>
		<item>
			<type>home</type>
		</item>
		<item>
			<type>internalLink</type>
			<title>Délibérations</title>
			<typeConf>
				<link>app_lacrau_tzen/delib</link>
			</typeConf>
		</item>
		<item>
			<type>internalLink</type>
			<title>Arrêtés</title>
			<typeConf>
				<link>app_lacrau_tzen/arrete</link>
			</typeConf>
		</item>
	</menu>
</ihm>
```

{% hint style="info" %}
Le chemin `app_lacrau_tzen/...` ci-dessus correspond au déploiement d'origine de cette configuration — à adapter à l'identifiant applicatif du projet en cours.
{% endhint %}
{% endstep %}
{% endstepper %}


---

# 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-efalia-portal.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.