Sites & Multi-Tenancy — Magic Varsh Docs

Magic Varsh can host many sites from a single platform. A site is a self-contained website: it has its own pages, navigation, content, media, forms, users, roles, settings and branding, and it is served at its own URL (for example /web/acme) or on its own custom domain.

Everything you build is automatically scoped to the site you are working in, so two sites never see or affect each other's content.

What is separate for every site

Pages, page layouts and navigation menus.
Portlets, dynamic forms and web content.
Digital assets (media library), including its own Trash and recovery.
Email templates and the Send-Email screen (only that site's templates are offered).
Users, roles, and site-specific list-of-values, labels and workflows.
Third-party integration components.
Settings — SMTP, SMS, SSL, media, language, and single sign-on / auth providers.
Scheduled jobs (a site can have its own jobs; the platform also has system-wide jobs).
Logs and their archives.

Some things are shared on purpose so you don't have to re-create them for every site: common roles (Administrator and Guest), shared reference data, and system-wide settings maintained by the platform administrator. A site can override shared reference data with its own values where needed.

The Site Administrator role

A Site Administrator manages exactly one site. They can administer that site's pages, content, users, roles and settings, but they cannot see or change other sites or platform-wide settings. This lets you delegate a whole site to a team without giving them control of the entire platform.

The platform-wide Administrator can work across all sites, and the Guest role is common to every site. See Users & Roles to assign the Site Administrator role.

Choosing the active site

In the admin console the sidebar shows an Active Site selector. A platform administrator can switch between sites (or choose All Sites to work across them); a Site Administrator is locked to their own site. Everything you create or edit while a site is selected belongs to that site.

Open the admin console and look at the Active Site selector near the top of the sidebar.
Pick the site you want to work in (Site Administrators are already fixed to their site).
Create pages, content, forms and settings as usual — they are saved to the selected site.

Because a Site Administrator is bound to one site, the site they can access is decided by the platform, not by anything sent from the browser — so site boundaries cannot be bypassed.

Themes

Each site can carry its own theme — the header, footer, page-body canvas and colours that wrap your content. Themes are managed from Settings → Branding → Themes: choose a bundle, preview it, and apply it to a site. Beyond header and footer, a theme can define a Content canvas (a template wrapping the page body and footer together) and a Footer JS slot for a custom script that runs after the footer — for example to initialise icons or wire up interactive page elements.

A theme's Content canvas and Footer JS are optional. Leave them blank and the site renders with the platform's built-in page canvas, so adopting a theme never breaks an existing site.

Custom domains

A site's public address doesn't have to be a path like /web/acme — you can point your own domain (for example www.acme.com) at it instead. Add the domain under Settings → Domains and choose which site it should serve; once the domain's DNS points at the platform, the TLS certificate is requested and renewed automatically — there is nothing to upload or configure with a certificate authority yourself.

Point the domain's DNS (an A or CNAME record) at the platform's public address.
Open Settings → Domains, add the domain, and choose the site it should serve.
Wait for the domain to show Active — the certificate is issued automatically the first time it's needed.

A domain shows Pending until DNS resolves correctly and its certificate has been issued; there is no manual certificate step.