How does RealMosaic separate admin editing from the public website

RealMosaic uses clear separation between authoring and public site delivery. Publishing happens in the admin system, while public delivery is read focused and designed for predictable output.

What access control features does RealMosaic provide

RealMosaic includes strong authentication, role based access controls, granular permissions for modules and actions, and separation between agency users and client editors.

How does RealMosaic reduce risk during changes

The platform uses change control practices focused on stability, including theme workflow history, diff and restore tools, plus publishing guardrails to reduce accidental layout or brand damage.

What does RealMosaic mean by reliability

Reliability on this page refers to cache friendly delivery patterns, clear failure boundaries between admin and public delivery, and operational practices designed to minimise surprises.

What is the shared responsibility model in RealMosaic

RealMosaic secures platform boundaries, infrastructure, and core workflows, while agencies control user access, client editor permissions, and publishing practices. Recommended settings are guided by risk profile.

Does the security page provide full technical implementation details

No. The page is intentionally high level. Deeper operational detail is covered during onboarding.

RealMosaic Security and Reliability, Stable Agency CMS Delivery

Platform boundaries

Clear separation between authoring and public site delivery
Public delivery is read focused, publishing happens in the admin system
Deterministic output to reduce surprises and support caching
Site isolation as a first principle

Access control

Strong authentication and role based access controls
Granular permissions for admin modules and actions
Clear separation between agency users and client editors
Permissions and guardrails to reduce accidental damage

Change control

Release discipline focused on stability
Theme workflow with history, diff, and restore for safer changes
Publishing guardrails to protect layouts and brand
Clear communication during early access and rollout

Reliability

Cache friendly delivery patterns designed for stable performance
Clear failure boundaries between admin and public delivery
Operational practices designed to minimise surprises
Escalation paths for platform level issues

What agencies can expect

Guided onboarding and recommended role settings
Support channels and escalation paths
Practical advice for permissions, publishing, and change workflow
Clear boundaries on platform responsibility versus agency responsibility

Shared responsibility

We secure the platform boundaries, infrastructure, and core workflows
You control who has access, and how client editors publish content
Good password and access hygiene improves security further
We recommend settings based on your risk profile

Book a demo View pricing Contact

Security and reliability