Municipalities, regional county municipalities, Crown corporations and other Quebec public bodies send thousands of emails a day on the organization's behalf. The signature attached to them is both an official calling card and a processing of personal information. For the public sector, three concerns stack up: data sovereignty, French-English bilingualism, and consistency across dozens of departments. A centrally managed tool resolves all three at once.
What concerns are specific to the public sector?
A public body does not face the same constraints as a small business. Email is an official channel, often subject to rules on language, accessibility and retention. Four requirements come up again and again:
- Data sovereignty: the personal information of citizens and employees must remain under a Canadian legal framework.
- Bilingualism: correspondence must be available in French, the official language, and sometimes in English depending on the recipient.
- Consistency: the organization's image must be coherent across public works, the clerk's office, senior management and elected officials.
- Compliance: Law 25 governs personal information, and a standardized confidentiality notice is often required.
Letting each employee compose their own signature makes all four requirements impossible to guarantee. Central management is the only realistic approach at the scale of a public body.
Data sovereignty and Canadian hosting
For a public body, knowing where data lives and where emails are routed is not a technical detail — it is a sovereignty question. Many signature solutions work server-side: every outbound email is relayed through the vendor's servers — sometimes abroad — to receive its signature. The message content, often carrying personal information, then leaves the country.
ATOM Signatures works client-side: an add-in inserts the signature directly in Outlook, at compose time. The email never leaves the body's Microsoft 365 infrastructure, and the configuration data is hosted in Canada. This is the architecture most aligned with the public sector's sovereignty expectations.
To dig deeper, see Canadian data residency and email data sovereignty.
How do you manage bilingual French and English signatures?
In Quebec, French is the official language of the administration, yet a public body regularly corresponds in English with certain citizens, partners or suppliers. The signature must reflect this reality without multiplying manual work.
With the visual editor, you build a template whose labels (phone, extension, website, notice) exist in both languages, then target it by Microsoft 365 group: a French version by default for everyone, an English variant for the departments that need it. The employee configures nothing — the right version applies automatically. The platform itself is bilingual FR-CA / EN-CA, which simplifies administration by a French-speaking team.
How do you standardize signatures across departments?
A public body often gathers dozens of units: directorates, departments, boroughs, committees. Without a central tool, each ends up using its own colours, logos and wording. Central management flips that logic:
- You define one or more official templates in the visual editor, in the organization's colours.
- You target each template to the matching Microsoft 365 groups (a department, a directorate, a borough).
- Each person's contact details fill in automatically from the directory, via Microsoft Graph, in real time.
- An update — new logo, changed address, new notice — propagates to the whole organization in one move.
The result: a coherent image on every email, whatever the sending department, with no action from employees.
| Public sector concern | Manual management | ATOM Signatures |
|---|---|---|
| Data residency | Variable, often outside Canada | Hosted in Canada, client-side |
| FR/EN bilingualism | Each employee improvises a version | Bilingual template targeted by group |
| Consistency across departments | Hard to maintain | Centralized, targeted templates |
| Updating a notice | Email to all staff | One change, propagated everywhere |
| Up-to-date contact details | Typed by hand, quickly stale | Directory via Microsoft Graph |
Law 25 and confidentiality notices
Public bodies are fully subject to Law 25, Quebec's reform of personal information protection administered by the Commission d'accès à l'information (CAI). A signature contains personal information (an employee's name, title, contact details): the body must know where it is hosted, govern any transfer outside Quebec, and be able to delete it.
Many bodies also add a confidentiality notice or an official-language statement at the foot of the email. This block can be built into the template and applied uniformly to the whole organization or to specific groups. Because the text is managed in the same place as the signature, it stays consistent and updates everywhere in one move.
Go further: email signatures and Law 25 and the confidentiality notice at the foot of an email.
This article is provided for information purposes and does not constitute legal advice. To assess your body's situation, consult a legal advisor or the Commission d'accès à l'information.
Why ATOM Signatures for the public sector
ATOM Signatures was built in Quebec to answer exactly this context:
- 100% Canadian hosting and client-side insertion: the email never leaves Microsoft 365.
- Bilingual FR-CA / EN-CA platform and signatures, administered by a French-speaking team.
- Targeting by Microsoft 365 group to standardize each department, directorate or borough.
- Real-time contact details via Microsoft Graph, drawn from the body's directory.
- Simple pricing: CAD $1 per user per month, all included — a predictable model for a public budget.
Frequently asked questions
Can a municipality's signature data stay in Canada?
Yes. ATOM Signatures hosts configuration data in Canada and inserts the signature client-side, inside Outlook. The email never passes through a third-party server abroad, which meets the data sovereignty expectations of the Quebec public sector.
How do we manage bilingual French and English signatures?
The visual editor lets you build a template with bilingual labels and target it by Microsoft 365 group. A body can apply a French version by default while offering an English variant to the relevant departments, with no action from the employee.
Can signatures be standardized across departments or divisions?
Yes. Signatures are managed centrally and targeted by Microsoft 365 group (department, division, borough). Each unit gets the right template, contact details fill in from the directory, and an update propagates to everyone at once.
Can a confidentiality notice be added to every signature?
Yes. A notice block (confidentiality, official language, accessibility) can be built into the template and applied to the whole organization or to specific groups. Because management is centralized, the wording stays consistent and updates everywhere at once.
Consistent public-sector signatures, hosted in Canada. ATOM Signatures automatically applies your body's official signature in Outlook, in French and in English, client-side and with 100% Canadian hosting.
Go further: email data sovereignty and targeting by Microsoft 365 group.
Sources
- Commission d'accès à l'information du Québec — cai.gouv.qc.ca
- Law 25 (official text) — LégisQuébec