Many brands. Many sites. One place to manage them.
Give every brand, campaign, and region its own site record, URLs, and theme, all managed from one studio.
- Site
- Group corporate
- CMS URL
- cms.example.com/corporate
- Preview URL
- preview.corporate.example.com
- Theme
- corporate
- Frontend
- corporate-webBuild passed
- Access
- Admin roles only
Every site, managed together.
Settings for every site
Each site is a tenant with its own entry in Studio settings. The entry holds what the site needs to exist: the CMS URL editors work in, the developer preview URL, the active theme, and the frontend that renders it.
- CMS and developer preview URLs
- An active theme per site
- Collections made visible per site
- Settings restricted to admin roles
Each site links to its live and preview versions
A frontend entry stores the head's live URL, preview URL, and build status, and links to its site. Editors switch between sites and frontends from the Studio sidebar, and open the live or preview site in one click.
- Live and preview URLs on the record
- Build status for each frontend
- Site and frontend switcher in the sidebar
- AI agents registered per frontend
Build a template once, reuse it across the group
Sites share the same layouts and widgets, and a new site can be cloned from an existing one. The frontend loads each site's theme at runtime, so one deployment serves sites that look nothing alike.
- Clone a new site from an existing one
- Shared layouts and widgets underneath
- A theme per site, loaded at runtime
- The default theme when none is set
Each site's content stays with that site
Every request is scoped by tenant, and collections carry a team field that keeps each site's items apart. Editors see and create items for the site they have selected, and permissions can limit users to their own sites.
- Requests scoped by tenant
- Items kept separate per site
- Permissions filtered to a user's sites
- Workflows assigned per site
Questions
Something else? Ask us directly.
No. Each site sets its own theme, and the frontend loads that theme's stylesheet at runtime. Sites can share layouts and widgets and still look completely different.
More in CMS.
CMS overviewSee Multisite management on a real site.
Book a demo and we'll walk you through it.