The meeting is online. Who controls the room?

What happened

On 26 January 2026, France announced plans to generalise DINUM’s Visio videoconferencing service across state services by 2027. The announcement describes a deployment programme, not a completed migration.

The Visio service page describes optional recording and transcription, and access for external participants when a meeting is opened to them. Its FAQ also states limits for restricted material and health-data use. Those boundaries matter alongside the hosting choice.

A conversation leaves more than a live video stream

Consider a public body discussing an infrastructure incident with a private operator. The conversation may include names, locations, diagrams and a decision about the next action. A recording, an exported file and a transcript can each create another version of that information. This is an illustrative scenario. The question for the organisations is which of those records they need, who is allowed to receive them and how they remain connected to the incident after the call ends.

These decisions should be made before a convenient feature is enabled by default. An organiser might need temporary access for a specialist without making that specialist a permanent member of the wider operation. Another participant may need to see a document without being able to obtain an unrelated case file. A transcription service introduces its own processing and retention questions. A technically successful call only answers whether people could communicate; the surrounding workflow must also establish what happened to the information they exchanged.

Sovereignty is a set of practical decisions

A European supplier can be part of the answer. So can local processing. Neither removes the need to examine identity providers, update mechanisms, support access and export formats. These dependencies matter when an organisation changes supplier, loses a connection or needs to withdraw a participant’s access.

• Control participation. Agree how staff and external partners join, how identities are checked and how access ends.
• Know the data path. Document where calls, files and optional transcripts are processed and retained.
• Plan continued operation. Establish maintenance, updates, support responsibilities and an exercised fallback.

Check the dependencies behind the European label

A procurement discussion can start with where software is built and where it is hosted, then follow the actual operating chain. Which service authenticates participants? Who can reset an account? Who installs updates and investigates a support request? Where are recordings, backups and model inputs processed? An organisation needs answers it can verify for the deployment it is accepting. A broad sovereignty claim does not answer these questions by itself, even when the supplier and customer are both European.

Continuity and change deserve the same attention. The organisation may need to move hosting, change an identity provider, export its records or transfer maintenance. Those options depend on interfaces, documentation, operating access and the contract, as well as the source code. They should be scoped and tested rather than assumed. France’s decision is a useful starting point for that discussion; it is not evidence that every European-built communications product has the same security properties or the same suitability for sensitive work.

Communications software built around the work

Meridian can develop standalone communications applications for messaging, voice, video and file sharing, with optional platform integration. Scope, encryption design, hosting and security acceptance are agreed for the project. Local AI transcription can be considered where appropriate, with explicit rules for access and retention. European sovereignty should be demonstrated through these choices and tested arrangements. It is not an automatic certification or an assertion of approval for classified work. Meridian has no claimed role in France’s Visio programme.

Define one communications workflow and evaluate it

A Meridian engagement could begin with one conversation between an internal coordinator, an approved external specialist and a field colleague. Users and technical teams would define how invitations are issued, what information may be shared and which outcomes become part of the operational record. The application could be standalone or connected to Meridian Platform through agreed interfaces. The delivery scope should describe what is being developed and integrated, rather than imply that every possible communications feature is already a packaged service.

The evaluation would follow the complete workflow: invite a participant, verify the appropriate identity, exchange an approved document, end access and check what remains in the record. If transcription is included, participants should be able to compare a summary with its source and correct mistakes before acting on it. A second exercise should make the primary channel unavailable and confirm the agreed fallback. Acceptance also needs evidence for the required encryption, access enforcement and operating controls. Building with operational users gives these requirements a concrete setting, while European control remains something the deployment must demonstrate.

Control of the conversation includes control of the systems around it.