Multi-site structure
Active site selection, templates and roles specific to each site, cross-site administration for corporate teams.
Use case 04
One platform, every site, every language
The same documentation standard everywhere, with each site's template and each team's languages.
The reality today
Three sites, three ways of documenting, no overall view
Each site built its documentation with the means it had. The templates differ, so do the levels of detail, and no one at head office can say how many critical procedures are actually up to date.
When a team arrives from another site, it has to relearn the format before it can grasp the substance. When a procedure exists only in French, some of the contractors misread it.
IT, meanwhile, inherits three tools, two directories and access granted by hand. Governance exists on paper, not in the system.
With Prism
One deployment, templates per site, shared governance
Prism is multi-site from day one: you choose the active site, and each site has its own role matrix, statistics and report template. Procedures automatically inherit their site's settings.
The governance standard, on the other hand, is shared: same roles, same approval workflow, same audit log, whatever the site. Management sees the real state of the document portfolio, site by site.
Translations are generated on demand, with a status for each language, down to regional variants. Generating a translation is a logged, permission-controlled action, like everything else.
| BEFORE | AFTER |
|---|---|
| A different template at every site | One template per site, inherited automatically |
| No consolidated view for management | Statistics per site: published, pending, languages covered |
| Access granted manually, site by site | Enterprise SSO and a role matrix per site |
| Translations redone by hand, when they exist | Generated translations, with a status per language |
FOR IT TEAMS
A deployment, not a project
Integrations
Azure AD SSO for authentication, SharePoint and the CMMS as destinations. Distribution is a separate right, enabled site by site.
Templates per site
Each site configures its accent color, logo, page structure and blocks. Procedures inherit them automatically.
Access governance
A role matrix specific to each site, and a simulated role to check a configuration before rolling it out to users.
FOR OPERATIONS LEADERSHIP
See the real state of your documentation
Traceability
Who wrote it, who reviewed it, who signed it, and when. All the way back to the source video, with a QR code scan.
Compliance
Versions, signatures, revision table, audit log. The attributes a quality or OHS standard expects.
Multi-site
A single deployment for several sites, with statistics per site: published, pending, languages covered.
Who it's for
The roles involved in this scenario
Operations leadership
They get a consolidated read on document compliance across their sites.
IT teams
They plug one tool into the existing directory instead of administering three.
Site admins
They configure their template and access without depending on head office.
Looking ahead
Your document portfolio becomes an asset, not a liability
From there, documentation stops being a permanent game of catch-up. It becomes an inventory of the group's operational knowledge: what's captured, what's approved, what's translated, and what's still left to do.
Let's look at your sites and your languages
A session with your IT and quality teams to scope the integrations, the templates and access governance.
