--- title: The group view description: Read every database of the group side by side, broken down by entity, with the total headcount and the thresholds reached, and find out who can open this view. url: "http://illizeo.com/en/centre-aide/bdese-group-view/" updated: "2026-11-11" category: BDESE --- # The group view A group of companies keeps several BDESEs: one per company governed by French law, or one per economic and social unit (ESU). The group view presents them side by side, broken down by entity, with the group’s total headcount and its position against the 50 and 300 employee thresholds. It is a consolidated reading, not a BDESE within the meaning of the French Labour Code. This article explains what the **Group view** tab is for, who can open it and how to read it. It is aimed at group HR management and the module’s administrators. ## Before you start - The BDESE module is installed and at least one database is declared in the [BDESE databases](https://illizeo.com/en/centre-aide/bdese-databases/) tab. - The tab requires the **BDESE group view** right at **Access** level. The Administrator and HR roles carry it; the Works council member, Works council expert and BDESE contributor roles do not. - It also requires a scope that covers every entity of every declared database. In practice, your role’s population must include all the companies concerned, as is the case for a role covering the whole workforce. - If you have the right without covering every entity, the tab is shown but displays the message “The group view is reserved for those covering every entity of the group.” ## Opening the group view 1. In the menu, open **BDESE › Group view**, or click the **Group view** tab from any other tab of the module. 2. The **Group** card appears, with the table of headcounts by database and entity. If no database has been declared yet, the message “No BDESE declared in the group.” appears: start with the BDESE databases tab. ## Reading the group table ![Group view tab: the sentence on where the headcount comes from, then the Group card with the Under 50 employees and Under 300 employees badges for the total; below, a two-column table, Database and entities and Headcount, with a single database, its Company badge and its headcount of 2, the row of its entity with its country and headcount, and the final Group row with the total of 2.](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/bdese-vue-groupe-01.en_-scaled.png?resize=800%2C351&quality=80&ssl=1) The databases, entity by entity, and the group total; here, a single database. The table has two columns, **Database and entities** and **Headcount**: - one row per database, with its label, its **Company** or **ESU** badge and its headcount; - under each database, one row per covered entity, with its country and its own headcount; - a final **Group** row, which carries the total. At the top of the card, the threshold badges apply to the group total: **50 employees reached** or **Under 50 employees**, **300 employees reached** or **Under 300 employees**. An entity whose headcount is unknown shows “—”. ### Where the headcount comes from Headcounts are those from France compliance, as in the BDESE databases tab: only contracts in France count. The group total is the sum of the known headcounts of every entity of every database. A sentence at the top of the tab recalls where the headcount comes from. If France compliance counts the headcount over the whole workspace, no entity has its own headcount. To see each entity’s headcount, choose the **Per sub-company** scope in **Settings › Compliance**, France card, **Medical visits and headcount** tab. ### What the table does not show The group view shows headcounts only. It shows neither fiscal year values, nor remuneration, nor confidential information. To consult a database’s content, go to the [Data](https://illizeo.com/en/centre-aide/bdese-data-entry-and-publication/) tab and choose the database you want. ## What the group view is for The group view helps you run the BDESE at group level: - check that every French company with 50 employees or more is covered by a database; - spot the databases that cross the 300 employee threshold, and whose default model may need reviewing in the [Structure](https://illizeo.com/en/centre-aide/bdese-content-structure/) tab; - check how entities are spread across databases, particularly for an ESU; - have a group total for your own analyses. It replaces no database. Each database keeps its structure, fiscal years, contributors and publications. The CSE of each company or ESU consults its own database, never the group view. ## Giving access to the group view To open the group view to a group HR manager: 1. Open the roles matrix and choose the person’s role. 2. Grant the **BDESE group view** right at **Access** level. 3. Check the role’s population: it must cover every entity of the declared databases. A role limited to its own sub-company is not enough: the person will see the tab, but with the restriction message. In that case, the [BDESE databases](https://illizeo.com/en/centre-aide/bdese-databases/) tab remains the right entry point: it shows the databases of the entities their role covers. ## Good to know - The group view presents the databases side by side; it does not merge them into a group BDESE. - It requires both its own right and a scope covering every declared entity. - It is read-only: it offers no actions. - The thresholds shown are for information and apply to the group total; each database’s model is chosen database by database. - A newly declared database appears in the group view at once; if it covers an entity your role does not cover, the view is closed to you until your role’s population is widened. ## Frequently asked questions ### I have the “Group view” right but I see a restriction message. Why? Your role does not cover every declared entity. Widen its population, or use the BDESE databases tab, which shows the databases within your scope. ### Do CSE members see the group view? No. The Works council member role does not carry this right; each member consults the database of their company or ESU. ### Why does an entity show “—”? Its headcount is unknown: France compliance counts the headcount over the whole workspace, or the entity has no counted contract in France. ### *Similaire*