Clark Rubber I YMCA I Randy's Worldwide I Frontier Touring
Admin, editor, author, developer, translator. Recognisable roles out of the box, each one a named bundle of what a person is allowed to do. Assign a role to a group rather than a person, so when someone joins or leaves you change the group, not a dozen separate settings.
Roles that fit how teams actually work.
Manages people, roles, and settings across the sites in scope. The role you give your platform owners, not your whole team. Everything an editor can do, plus the keys to how access itself is configured.
The everyday operator role. Makes changes and pushes them live across the properties you assign, and nowhere else.
Work goes live only once an editor approves it. Built for junior team members and local contributors who should propose changes, not ship them.
Templates, components, and integrations. Full access to the build layer, with no access to commerce or customer data.
Keeps localisation moving without any risk to the master content. A translator works only in the languages you assign.
When none of the presets fit, build your own: choose exactly what the role can do and where, save it, and reuse it across people.
The same role can reach a single page, a section, a whole site, or your entire portfolio. This is how head office keeps brand and pricing control while every location runs its own content. One role definition; the reach is yours to decide.
Outside people get their own account type, a scoped role, and an end date. They see only the sites and tasks you assign, edit only their own work, and lose access the moment the engagement ends. No shared logins, no cleaning it up later.
Enterprise control, without the enterprise overhead
The governance a security team expects, run by a team that doesn't include a security specialist.
Connect your existing identity provider, so access here follows the same joiner-mover-leaver process as the rest of your stack. One set of credentials, one place to switch them off.
When someone joins or leaves your directory, their access here follows automatically. No orphaned accounts, no manual cleanup.
Every page keeps a complete version history with who changed what and when, and one-click rollback to any earlier version.
SOC 2, ISO 27001, and GDPR compliant, hosted securely. The boxes procurement needs ticked, ticked.
When you run a change across every property from a single prompt, it runs inside the scope of the role that launched it. The same permissions that govern your people govern your agents. That is what makes one prompt across seventy sites safe to buy, not just fast.
New accounts start with no access. You grant only what is needed - the security default of deny first, allow on purpose.
Access set on a section flows to the pages inside it, unless you override it.
Changing content and making it live are different rights, held by different people.
Every change records who, what, where, and when.
Outside accounts carry an expiry and a tight scope.
Automated actions obey the exact permissions your people do.
Most teams model their roles and scope them to their properties in the first week, then bring people in and turn on automation with the boundaries already in place.
Start from the presets, add a custom role where you need one.
Point each role at the sites, sections, or pages it owns.
Internal teams and outside contributors, each sandboxed to their scope.
Automate across every property knowing each action stays inside the scope you set.
Book a 20 min demo