Governance and control
Stay in control of your entire digital estate.
Forrit gives content, technology and governance teams clear control over how digital experiences are created, approved, published and operated. Define who can make changes, govern how those changes reach production, standardise how environments are deployed and run, and keep a clear record of what happened.
- 01
Give people the capabilities they need, without giving everyone admin access.
- 02
Changes reach production deliberately, never accidentally.
- 03
Standardise how environments are provisioned, deployed and operated.
- 04
See what changed, who changed it and how it was approved.
One cloud-native platform · Forrit CMS + Service Delivery Hub
Control doesn't mean restricting your teams. It means freedom within clearly defined guardrails.
01 · People
Control who can do what.
Not everyone who works on your digital estate needs the same access. Editors, reviewers, approvers, developers and administrators all do different jobs, and handing out administrative rights just to keep work moving is how mistakes and risk creep in.
Forrit supports custom roles with feature-level permissions, so you can give people the capabilities their job needs without giving everyone admin access. Sign-in runs through your enterprise identity provider, and creating, reviewing, approving and administering content can be kept as separate duties, which is exactly what regulated organisations need to show.
Separation of duties, built in
An editor creates and previews the change
A reviewer checks it and asks for edits where needed
An approver signs it off for publishing
An administrator manages users and roles, separately from content
People capabilities
CMS roles and permissions
Decide exactly who can create, edit, approve and publish, enforced consistently across sites, teams, agencies and subsidiaries.
Custom roles
Create roles that match how your organisation works, such as editor, approver, developer or administrator, and choose which features each one can use.
Single sign-on and MFA
People sign in through your enterprise identity provider, with single sign-on, multi-factor authentication and conditional access.
Least-privilege access
Role-based access control gives every person and service only the permissions they need, and nothing more.
Access scoped by project
Give a regional team, brand or agency access to its own project, without opening up the rest of your digital estate.
A role-based interface
Whether someone is editing copy, building components or monitoring operations, the interface focuses them on the task their role covers.
02 · Publishing
Changes reach production deliberately, never accidentally.
In many content management systems, an edit is one click away from your live site. That's fast, right up until the wrong price, the wrong date or an unapproved claim reaches your customers.
Forrit puts a managed path between making a change and that change going live. Work is prepared in tasks, previewed, reviewed and approved through the workflows you configure, and only then published. Larger pieces of work, such as a rebrand or a product launch, can be prepared in their own task while everyday publishing carries on.
From draft to live
Create: the change is made in a task, away from the live site
Preview: see exactly how it will look before it goes anywhere
Review: reviewers check the change and request edits where needed
Approve: named approvers sign off through your workflow
Publish: approved content goes live, with rollback if plans change
Publishing capabilities
Approval workflows
Customisable workflows and tailored approval policies control what gets published, all tied back to each user's identity.
Preview before publishing
Reviewers and approvers see changes in context before they go live, so they judge what customers will actually see.
Parallel tasks
Different people and teams can work on different changes at the same time, each in its own task, without overwriting each other's work.
Release history and rollback
Changes are prepared in task branches and previewed before going live. Release history and full rollback let you reverse a change quickly.
Safe publishing lifecycle
Test, staging and live environments, task branches and full rollback let many teams work in parallel without risking production.
AI under the same controls
Changes made by an authorised AI assistant through the Forrit MCP server land in task branches, just like changes made by people, so they are reviewed and approved before anything is published.
03 · Platform
Control your digital estate, not just your CMS.
CMS governance usually stops at the content. Behind it, environments are often provisioned by hand, configured differently for every project and monitored in separate tools, which makes the estate harder to secure, audit and run.
The Forrit Service Delivery Hub brings environments, infrastructure and operations into the same operating model. Provisioning and configuration become repeatable and templated, and IT gets one operational view across tenants, subscriptions, environments and clusters. IT controls how the estate is provisioned and operated; content teams control what gets published.
Every environment, the same governed way
Start from a repeatable template, not a bespoke build
The Service Delivery Hub provisions it through a simple seven-step process
Every deployment is fully managed and audited
The environment joins one operational view of your whole estate
Platform capabilities
Repeatable, templated environments
Provisioning and configuration become a repeatable platform capability, rather than a separate engineering exercise for every deployment.
Tenants to clusters, in one view
See and manage tenants, subscriptions, environments and clusters from a single operational view, instead of a collection of separate consoles.
Audited deployment in minutes
The Service Delivery Hub's seven-step process creates each environment accurately, with every deployment fully managed and audited.
Restricted production access
Access to production environments is tightly restricted, with IP restrictions applied where appropriate.
Your cloud, your ownership
Your Forrit environment can live in your own cloud tenant and subscription. You own the resources, your assets stay in your subscription and you keep control of perimeter security, including any extra layers you add around Forrit.
Real-time monitoring and alerts
Global real-time monitoring identifies performance issues quickly, and system alerts tell you when a service isn't working as expected.
04 · Accountability
Know what changed, who changed it and how it went live.
Control isn't much use without accountability. When an auditor, a regulator or your own leadership asks what happened, you need an answer, not a hunt through old emails.
Forrit captures user activity in an audit history covering sign-ins, content changes, workflow actions and administrative activity. You can follow any change from the person who made it, through review and approval, to the release that published it, and export the records when you need to share them.
What the audit history records
Authentication: who signed in, and when
Content changes: what was created, edited or removed, and by whom
Workflow actions: who reviewed, approved or sent back a change
Administrative activity: changes to users, roles and settings
Accountability capabilities
Complete audit trail
Every CMS task, action and change is securely logged, giving you an audit history of who did what, and when.
End-to-end change history
Follow any change from the person who drafted it, through review and approval, to the release that published it.
Named approvals
Approvals are tied to the identity of the person who gave them, so sign-off is never anonymous or assumed.
Records you can review and export
Review audit records in the CMS, and export them when your compliance, risk or internal audit teams need them.
External links audited
External URLs are audited from the very start of the publishing workflow, alongside media scanning.
Evidence for audit and regulation
A clear record of change and approval helps you evidence governance to auditors and supports obligations such as DORA and operational resilience.
Freedom within guardrails
Standardise what should be controlled. Keep flexibility where it matters.
Control can sound like locking everything down. It shouldn't. Central governance doesn't require every site, brand or business unit to work in exactly the same way.
In Forrit, multiple projects share one platform while keeping their own users, permissions, workflows and deployment rules. Security, identity and brand standards are set once and apply everywhere; how each team works within them is up to them. And because Forrit is a hybrid headless CMS, developers keep the freedom to build experiences their way.
What to standardise, and what can vary
Standardise: security controls, identity and production access
Standardise: approved components, brand rules and environment templates
Vary: who works on each project, and what they can do
Vary: workflows, approval routes and deployment rules for each team
Vary: how developers build each experience, as HTML or headless
Flexibility capabilities
Multi-tenancy
Run one site or a thousand from one platform, with projects that group the content and endpoints for each site, brand or business unit.
Workflows that fit each team
A regulated product site and a careers site don't need the same approval route. Each project can have its own workflows and rules.
Governed, reusable components
Build brand and accessibility patterns into components once, then reuse them across sites, so rebrands and campaigns stay consistent.
Freedom for developers
Hybrid headless architecture and .NET SDKs let developers use familiar tools and deliver content as HTML or JSON to any channel.
Onboard new business units
Bring new departments or acquired businesses onto the platform with their own project and roles, inside the guardrails you already have.
Public or sovereign cloud
Cloud native and deployable on leading public cloud platforms or with sovereign cloud providers, to meet data residency and sovereignty requirements.
Control for every team
Each team controls what it is accountable for.
Control in Forrit isn't one team holding all the keys. Content, compliance, IT and development teams each get the controls that match their responsibilities, on the same platform and under the same governance.
Content teams
What gets created
Create, edit and preview content in tasks using approved, reusable components, then submit it for review when it is ready.
Compliance and risk
What gets approved
Act as named approvers in your workflows, so nothing reaches customers without the right sign-off, and review the audit history afterwards.
IT and operations
How the estate is run
Provision, deploy, monitor and maintain every environment through the Service Delivery Hub, with production access tightly restricted.
Developers
How experiences are built
Build components with .NET SDKs and familiar tools, and deliver content as HTML or headless JSON, within the guardrails the platform provides.
Governance and control questions, answered
In Forrit, control covers four things: who can make changes (custom roles and permissions), how changes reach production (tasks, review and approval workflows), how environments are provisioned and operated (the Service Delivery Hub), and what happened afterwards (audit history). Together they give teams freedom to work within clearly defined guardrails.
You create custom roles, choose which CMS features each role can use, and assign roles to people who sign in through your enterprise identity provider. Permissions are set at feature level rather than on individual pages or items. To separate teams, brands or business units, give each one its own project with its own users, roles and workflows.
Yes. Because roles are defined by the features they can use, you can keep creating, reviewing, approving and administering content as separate duties. This separation of duties is often a requirement for regulated organisations, and every action is recorded in the audit history.
Changes are made in a task, previewed and then moved through the review and approval steps you configure. A change is only published once the required approvals are in place, and each step is tied to the identity of the person who took it. Release history and rollback let you reverse a change quickly if you need to.
Yes. Each change is prepared in its own task, so different people and teams can work in parallel without overwriting each other. A larger piece of work, such as a rebrand, can be prepared and previewed in its own task while everyday updates continue to be reviewed and published.
The audit history captures user activity including authentication, content changes, workflow actions and administrative activity, such as changes to users and roles. Records can be reviewed in the CMS and exported for compliance, risk or internal audit teams.
The Service Delivery Hub is the operational control plane for your Forrit estate. It provisions environments from repeatable templates through a simple seven-step process, manages and audits deployments, and gives IT one view of tenants, subscriptions, environments and clusters, with monitoring, scaling, cost tracking and patching managed centrally.
Yes. Multiple projects can share one Forrit platform while keeping their own users, permissions, workflows and deployment rules. Central governance doesn't require every site to work identically: you standardise security, identity and brand controls, and let each team work in the way that suits it.