What you can change, and what you cannot

The demo is a real installation, not a simulation, so it comes with real limits. Everything below is enforced by the server: none of it depends on hiding a button.

Yours to break

When you register, you get your own copy of the demo: the data, and the definitions that make the application. Inside that copy you can:

Use the application as any operator would: create, edit and delete records, upload documents, run the analysis pages.
Build new pages and change the ones that are there. Open your sandbox from the Designer with the credentials on this page and work on the metadata itself: pages, database statements, reports and the menu are yours to create, change and break.
Upload your own icons and images, which stay in your copy and are available to every demo project you open.
Start over whenever you want. Recreating the sandbox restores the original data and definitions, and nobody else is affected.

This is the point of the exercises: you are meant to build real pages, and there is nothing here you can damage that a single click will not restore.

Where the line falls

The main limit is the one the platform is about: you can build anything that is expressed as metadata, and nothing that requires code. Standard pages, whatever their shape, are metadata, which is why a whole application can be built here. A page with custom behaviour written by hand is not, and that stays out.

Beyond that, some things live outside your copy because they are shared by everyone using the demo, or because they belong to the installation rather than to a project. They are readable, and the application uses them normally, but they cannot be written from a demo account:

New dashboards. The ones that exist run normally and you can look at them, but creating them belongs to the administration side of GTmeta.
Translations: the language of an application is set once for everyone who uses it.
The AI configuration: the analyzer definitions, the chat settings and the shared prompts. The features work, but their setup is fixed.
The administration of the installation: projects, users, roles, profiles, database connections and their passwords, and the configuration of GTmeta. This is the part that governs every customer on the server, so it is reserved to the administrators of the installation.
Other projects. A demo session is granted one project at a time, and naming a different one gets you a refusal, not a different set of data. The Designer's upload tools are limited accordingly: there is no reaching the metadata of the installation and no listing of the projects on it.
Unlimited AI. The assistant and the analysis features work, within a usage allowance. It is a real service with a real cost behind it, and the allowance is what lets us leave it switched on for everybody.

Why it is drawn this way

A demo that could be locked down by hiding menu entries would not tell you anything about the platform, because the answer to "what stops the visitor" would be "nothing, we just did not show the button". Here the line is drawn on the server and checked on every request, including the ones the browser never sends.

That is also the honest answer to a question a technical evaluator should ask: the same mechanism that keeps one visitor out of another visitor's copy is what keeps one customer out of another customer's data on a shared installation.

Contact Us