Multi-site CMS for insurance: from service portal to performance portal

A multi-site CMS for insurance runs the public websites, the customer portal and the broker portals of an insurer, a mutual or a broker from a single governed platform. It has to meet three requirements at once. Every piece of content is approved before it goes live, sensitive data stays protected and business teams publish without waiting for a developer.

In 2026, a fourth requirement joins them. The customer portal can no longer just answer requests, whether that is a certificate of insurance, a claim to file or a policy to check. Connected to the CRM, it becomes a lever for the customer relationship. Jahia and Efficy call this shift moving from a service portal to a performance portal. This article explains what an insurance content management system must do to get there, then the criteria for choosing one.

What is an insurance content management system?

An insurance content management system is a web content platform that powers the websites, portals and apps of an insurance organization, with permissions, approval workflows and version history suited to a regulated industry. It is different from document management (ECM), which stores policy and claims files inside the core administration system.

The CMS handles what the policyholder, the prospect or the broker sees online. That includes product pages with coverage and exclusions, quote tools, embedded application journeys, legal documents and the personal space where policyholders find their policies. A group often adds the sites of its brands, its agency networks and its countries.

When the platform adds personalization, A/B testing and a customer data platform (CDP), it is called a DXP, or digital experience platform. That is the case of Jahia DXP, which combines the Jahia CMS with jExperience.

Why move from a service portal to a performance portal?

Because a customer portal that only answers requests leaves value on the table. Every visit says something about the policyholder's needs. Connected to the CRM, the portal can test an assumption about interest, measure the response and pass the signal on to the sales teams.

The service portal, what policyholders come for

A customer portal is first a service portal. Policyholders come to download a certificate, file a claim or check their policies. Their reasons for logging in vary and follow a seasonal pattern you need to account for. At the start of the school year, for example, families come to download their liability insurance certificate.

That service moment is a touchpoint the insurer did not have to create. The policyholder is logged in, identified and paying attention. This is where the performance portal begins.

The performance portal, testing and connecting to the CRM

The CRM forms an assumption from the policyholder's profile, for example a possible interest in car insurance, retirement savings or new coverage for a child. The portal tests it by adapting the content shown to that profile. The policyholder's response feeds a purchase-intent score that flows up to the CRM and back down to the portal.

The approach relies on two roles rather than two products. The CRM remains the master of the data and orchestrates the rest of the relationship, from first contact to signature. The portal is the touchpoint where you test and personalize. Jahia and Efficy walked through this scenario, from assumption to signed contract, in a French-language webinar for insurers and mutuals. The integration between the two platforms is described on the Efficy technology partnership page.

What to measure

The final metric remains the policy sold. Intermediate metrics, such as clicks on an offer or quotes started, help you steer but are always read against that outcome. An assumption that works is replicated on other segments and one that fails is dropped. The portal improves through continuous iteration.

Which obligations should an insurance CMS help you meet?

A CMS helps an insurer prove what was published, by whom and when. Approval workflows, version history, role-based permissions, publication audit trails and archiving are the functions to check first. Compliance itself stays with the insurer and its legal teams.

The obligations that apply to an insurer differ from one market to the next. Your compliance team defines them. The CMS has to make them easy to apply and easy to evidence when a product page, a legal notice or a disclosure is questioned.

The functions to check

• Approval: different workflows depending on how critical the content is, with a legal or compliance step for product pages and contractual documents.
• Versions: the history of each piece of content and the ability to roll back to an earlier version.
• Permissions: who can edit what, by role, by site and by product line.
• Audit trail and archiving: proof of what was online on a given date.
• Shared content: a legal notice updated once and reused on every site that carries it.

DORA and the European Accessibility Act, for insurers operating in the EU

Two European texts matter when an insurer active in the European Union chooses a CMS. Regulation (EU) 2022/2554, known as DORA, has applied since January 17, 2025 to insurance and reinsurance undertakings, except the smallest ones that the Solvency II Directive excludes from its scope, as well as to insurance intermediaries that are not micro, small or medium-sized enterprises. Among other things, it governs the risk tied to ICT third-party service providers, a category that includes the vendor that hosts or maintains your platform.

Directive (EU) 2019/882, the European Accessibility Act, has applied since June 28, 2025. It does not name insurance as such. It covers, among others, consumer banking services and e-commerce services, defined as services provided at a distance with a view to concluding a consumer contract. An online application journey offered to EU consumers therefore deserves a review with your legal team. On the tooling side, Jahia's Page Quality audit checks page accessibility against WCAG levels A, AA and AAA.

Why does an insurance group need a multi-site CMS?

Because a group rarely runs a single site. Brands, agency networks, countries and audiences such as individuals, professionals or businesses are published from one platform, with shared components and content, while each site keeps its own identity.

AG2R La Mondiale, a French social and wealth protection group, brought four previously separate sites together into a single portal, for the group, businesses, individuals and professionals. Twenty contributors have published content there with Jahia's contribution interface. The site of its food industry health prevention center was built in two months. The details are in the AG2R La Mondiale customer story.

Covéa, for its part, runs four Jahia platforms, one at group level and one for each of its brands. The functional modules are shared, which does not stop each brand from keeping its own identity.

The multi-site model also affects cost and security. A shared platform is maintained, upgraded and audited once for every site, which frees resources to run more projects in parallel. Our multisite CMS guide details the features to look at.

What security and sovereignty should you require from your CMS?

Verifiable proof, published by the vendor. Ask the vendor for its certifications, the scope they cover and the hosting options of its platform, then compare them with your security policy.

A majority of insurers already write sovereignty into their tenders. According to a survey run by Infopro Digital Études for L'Argus de l'assurance and Efficy, online from March 23 to April 10, 2026 among 412 decision-makers in France, 211 of them in insurance, insurance decision-makers answered as follows.

• 87% have added or plan to add digital sovereignty as a criterion in their tenders.
• 57% rank data security guarantees in their top 3 criteria when choosing a digital solution.
• 53% already have governance dedicated to digital sovereignty.

We turned this survey into a scoring grid in our article on digital sovereignty criteria for an IT RFP.

On Jahia's side, the Trust Center publishes the certifications in force. The ISO 27001:2022 certification covers the information security management system, from cloud to support and professional services. PCI DSS SAQ A compliance, assessed every year, lets customers run e-commerce sites where card payment processing is fully outsourced. Contributor accounts can be protected with multi-factor authentication. Jahia is a European company and an open-core platform. It is available as managed PaaS, in a private cloud or as an on-premise installation, depending on your data sovereignty constraints and regulatory requirements.

What role should AI play in an insurance CMS?

A useful one for editorial teams, provided you stay in control of the data and of approval. According to the Infopro Digital Études survey for L'Argus de l'assurance and Efficy (March-April 2026), 86% of insurance decision-makers in France factor digital sovereignty into their AI projects.

Jahia is a CMS with built-in AI. The CKEditor 5 editor includes an AI assistant compatible with OpenAI, Azure OpenAI, AWS Bedrock and Anthropic, so the insurer chooses its model provider. AI-assisted translations speed up the rollout of content in several languages. The Page Quality audit flags accessibility, SEO and readability issues. Content drafted with AI stays subject to the approval workflows you have defined, like any other content.

How do you personalize the customer portal without relying on developers?

By giving marketing and customer service teams tools they can run on their own. Page Builder is used to compose pages. jExperience personalizes content by segment and runs A/B tests on variants. Augmented Search helps policyholders find the right information in the portal.

A digital manager at an insurance group sums it up in a review published on G2, quoted on our data-driven personalization page: "I love that marketing teams can build landing pages without involving developers. Clients get excited about the personalization features." Jahia is rated 4.4 out of 5 on G2 from 603 reviews, as of October 7, 2026.

For integrations, the platform connects to the CRM, to quoting and application tools and to the existing IT landscape. StackConnect gives access to more than 1,000 connectors.

How do you choose a CMS for insurance websites and portals?

By checking seven points against evidence, during a demo or a proof of concept on one of your real journeys.

• Governance: configurable approval workflows, permissions by role and by site, version history, archiving.
• Multi-site: brands, agencies and countries managed on one platform, with shared content.
• Security: published, verifiable vendor certifications, multi-factor authentication, a known certification scope.
• Hosting: vendor PaaS, private cloud or on-premise, depending on your sovereignty policy.
• Integration: connection to the CRM, quoting tools and IT landscape without rebuilding the portal.
• Accessibility: WCAG checks built into the editorial work.
• Business autonomy: pages, personalization and tests in the hands of marketing teams.

To see how Jahia works as a multi-site CMS for insurance and meets these criteria for the customer portal, the broker portal and the public website, visit our insurance portals page.