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.

The four pillars of control in Forrit: people, publishing, platform and accountability, all on one cloud-native platform made up of the Forrit CMS and the Service Delivery Hub. Select a pillar to read more.
  1. 01

    People

    Give people the capabilities they need, without giving everyone admin access.

    • Custom roles
    • Feature-level permissions
    • Single sign-on & MFA
    • Separation of duties
  2. 02

    Publishing

    Changes reach production deliberately, never accidentally.

    • Tasks
    • Preview & review
    • Approval workflows
    • Release history & rollback
  3. 03

    Platform

    Standardise how environments are provisioned, deployed and operated.

    • Service Delivery Hub
    • Repeatable environments
    • Audited deployments
    • One operational view
  4. 04

    Accountability

    See what changed, who changed it and how it was approved.

    • Audit history
    • Named approvals
    • Admin activity
    • Exportable records

One cloud-native platform · Forrit CMS + Service Delivery Hub

Control doesn't mean restricting your teams. It means freedom within clearly defined guardrails.

Last updated

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

  1. An editor creates and previews the change

  2. A reviewer checks it and asks for edits where needed

  3. An approver signs it off for publishing

  4. An administrator manages users and roles, separately from content

Illustration: example roles and the features each one can use. You create your own custom roles to match how your organisation works.

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

  1. Create: the change is made in a task, away from the live site

  2. Preview: see exactly how it will look before it goes anywhere

  3. Review: reviewers check the change and request edits where needed

  4. Approve: named approvers sign off through your workflow

  5. Publish: approved content goes live, with rollback if plans change

Illustration: an everyday update and a larger piece of work move through preview, review and approval in separate tasks. Nothing reaches the live site until it is approved.

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

  1. Start from a repeatable template, not a bespoke build

  2. The Service Delivery Hub provisions it through a simple seven-step process

  3. Every deployment is fully managed and audited

  4. The environment joins one operational view of your whole estate

Illustration: the Service Delivery Hub provisions environments from repeatable templates and gives IT one operational view across tenants, subscriptions, environments and clusters.

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

  1. Authentication: who signed in, and when

  2. Content changes: what was created, edited or removed, and by whom

  3. Workflow actions: who reviewed, approved or sent back a change

  4. Administrative activity: changes to users, roles and settings

Illustration: an audit history follows a single change from sign-in and editing, through review and approval, to release.

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

  1. Standardise: security controls, identity and production access

  2. Standardise: approved components, brand rules and environment templates

  3. Vary: who works on each project, and what they can do

  4. Vary: workflows, approval routes and deployment rules for each team

  5. Vary: how developers build each experience, as HTML or headless

Illustration: three projects on one platform, each with its own users, roles and approval route, all inside the same security, identity, brand and environment guardrails.

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

Want to see it in action?

Book a demo