Page Settings
Who can open each page, its address, and its title and description
Every app has a Home page at /. Site apps can add more pages, each with its own address, access mode and settings. You manage them in the Pages tab — or simply ask the App Builder in chat.
When to create a separate page
Create a new page when:
- you want its own address that people can bookmark or share;
- it needs a different access mode (for example one public page in an internal app);
- it is a main destination, such as
/pricing,/docsor/account/orders; - it needs its own title and description for search engines and link previews.
Keep it inside an existing page when it is a dialog, a tab, a filter, a step of a wizard or another view of the same screen.
Examples
- "Product list" and "Product detail" → two pages (
/products,/product?id=…). - "Edit product" popup → stays on the product page.
Access modes
| Mode | Who can open it | Typical use |
|---|---|---|
| Public | Anyone with the address, no sign-in | Landing pages, public forms, catalogs |
| Operator User | Signed-in Operator users | Team tools that don't need ERP.net |
| ERP.net Internal User | Signed-in Operator users connected to ERP.net as internal users | Screens working with ERP.net data |
Public is available only on the Site plan.
The app's access mode
The app's access mode controls who can open the Home page and is the default for every new page. Change it in the Pages tab on the Home row.
New apps start with:
- ERP.net Internal User when an ERP.net instance is connected;
- Operator User otherwise.
Mixing access modes
Access is decided per page. In one app you can have:
/— Public landing page,/order-status— Public,/admin— ERP.net Internal User, for your team.
A visitor opening /admin is asked to sign in; the public pages open for everyone.
Ask: "Add an internal page at /admin, only for our ERP.net users, that lists today's web orders."
Page addresses
- Public pages:
https://app.operator.net/p/<app-slug>for Home,https://app.operator.net/p/<app-slug>/<page-path>for others. - Sub-pages nest:
account/ordersis served at/account/orders. - Links can carry details after
?— for exampleproduct?id=123— and the page reads them to show the right item. - Find the address to share in the Pages and Deploy tabs.
Page settings
Each page in the Pages tab has:
| Setting | What it does |
|---|---|
| URL path | The page's address, lowercase letters, digits and / — for example reports/sales |
| Title | Shown in the browser tab and link previews |
| Description | Shown in search results and link previews |
| Access mode | Who can open the page (see above) |
| Published | Unpublished pages show a Draft badge and cannot be opened |
| Sort order | Order of the page in the list |
The page's files live in a folder matching its path, for example pages/reports/sales/. The App Builder keeps the folder and the path in sync when you rename or move a page.
Data on public pages
A public page has no signed-in visitor, so it can't use your ERP.net connection, tables, files or secrets. Server data comes only through web requests marked Public, which use their own stored login. See Build Sites.