---
title: "From the Visual Site Manager (VSM) to the Page Builder: A transition guide for administrators"
slug: "from-the-visual-site-manager-vsm-to-the-page-builder-a-transition-guide-for-administrators"
updated: 2026-01-09T12:07:49Z
published: 2026-01-09T12:07:49Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.deltatre.com/llms.txt
> Use this file to discover all available pages before exploring further.

# From the Visual Site Manager (VSM) to the Page Builder: A transition guide for administrators

This article covers changes that the Page Builder introduces for administrators:

## Introduction

With the VSM, administrators configure permissions and metadata on a unique administration page (*Forge->Administration*) with content configurations (like custom entities or reference fields). Instead, Page Builder provides dedicated pages ([*Permissions*](/v1/docs/from-the-visual-site-manager-vsm-to-the-page-builder-a-transition-guide-for-administrators#permissions) ![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/20163398676764.png) and [*Metadata*](/v1/docs/from-the-visual-site-manager-vsm-to-the-page-builder-a-transition-guide-for-administrators#metadata) ![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/20164573788828.png)).

![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/20163398677916.png)

Regarding the [site structure import and export](/v1/docs/from-the-visual-site-manager-vsm-to-the-page-builder-a-transition-guide-for-administrators#site-structure-import-and-export), the Page Builder maintains the same experience as the VSM.

Finally, the Page Builder provides the brand new possibility to define the building blocks of the site structure: templates, layouts, and modules. A set of building blocks is known as a [context](/docs/from-the-visual-site-manager-vsm-to-the-page-builder-a-transition-guide-for-administrators#h_01JVPC3GNWMYQ56H6GRCGAF71N).

## Permissions

Since Page Builder 1.0.0 ([Release notes - FORGE Q2 '24](/v1/docs/release-notes-forge-q2-24)), the VSM and Page Builder have had separate permissions management.

| **VSM** | **Authorization groups definition** From*Forge->Administration->CONFIGURATIONS->Access Control List*, create access control permissions — each being named as *name_acp*. That creates a *CanOperateOn.Vsm.{name_acp}* permission for each *name_acp*. ![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/20164587649436.png) **Authorization groups assignment** - From GUIShell, assign *CanOperateOn.Vsm.{name_acl}* permissions to relevant roles. ![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/20208686902940.png) - Then, assign those roles to users who must access the site structure elements that those permissions limit in visibility. ![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/20206637295260.png) |
| --- | --- |
| **Page Builder** | **Definition and assignment of authorization groups** A streamlined process allows administrators to create and assign authorization groups within the same *Permissions* page. ![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/20164697680412.png) Also, the Page Builder allows defining permissions at the module, layout, and template level. For example, administrators can create groups that let editorial teams see only a few modules of the page they are on. For more information, read [Permissions](/v1/docs/permissions). |

## Metadata

Administrators gain a dedicated page in the Page Builder.

| **VSM** | F*orge->Administration->CONFIGURATIONS->Metadata* ![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/20206637296028.png) |
| --- | --- |
| **Page Builder** | ![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/image(251).png) For more information, read [the article dedicated to metadata](/v1/docs/metadata). |

## Site structure import and export

From the VSM to Page Builder, the feature's skin gets beautified, but the import and export behaviors remain the same.

| **VSM** | **![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/20163785357468.png)** |
| --- | --- |
| **Page Builder** | ![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/image(252).png) For more information, read articles on the import and export of the [site structure](/v1/docs/site-structure-export-and-import) and [navigation rules](/v1/docs/navigation-rules-export-and-import). |

## Context ingestion

Unlike the VSM, which only lets editorial teams create pages with the built-in templates, layouts, and modules (collectively called *context*), the Page Builder lets administrators ingest bespoke ones.

See [Add templates, modules, and layouts to pages](/v1/docs/add-templates-modules-and-layouts-to-pages) for more details about using contexts as page types.

When creating a page in the site structure, editorial teams select which context they will use by choosing the *Page Type*. This choice cannot change once the page is created.

In the example below, by choosing the Deltatre *Page Type*, editorial teams get the set of templates, layouts, and modules that administrators ingested in the Deltatre context.

![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/20206637296924.png)