Your public face
Your public face
Who can do this: Edit on the item you publish. Changing the space's Published switch needs Owner. Assets: browse with Read, change with Edit. See the .
What it's for
Some things in your space can be seen by anyone with a link, without signing in: a document, a table, a form, a dashboard, a shop or a booking site. This chapter covers how to make an item public, how to keep it narrow, how to give a site its own web address and look, and how to manage the images and files those pages use.
Public is different from the customer portal. The portal shows signed-in customers only what you expose to them. Public pages show everyone the same thing. For the portal, see .
Before you start
You need Edit on the item. The server checks it again when you press Publish.
Shops and booking sites need extra setup by your administrator (see below).
Needs your administrator: a shop or booking site only goes live on the web if an operator has registered a storefront template for that site type (System, Config, Deployments). If the Publish to web panel says no templates are configured, or says the template has no default host suffix, ask your administrator to register one. Attaching your own domain may also need a hosting integration; the panel says so when it is missing.
1. Publish a document, table, dashboard or form
Open the item's menu in the navigator and choose Publish. The menu offers it only for documents, data tables, dashboards, forms, sites and app connections. Other types (for example spreadsheets) have no public page.
The dialog is titled Publish Document for every type.
Check Document Slug. It is the item's address part. The dialog fills it from the first heading. If another item in the space already uses it, you see This slug is already used in this project.
Public: listed in the space's public navigation and search.
Only by link: reachable only by a secret link. Not listed.
Decide on Include in the navigation tree. Turn it off to keep a published item out of the public sidebar and search while its direct link still works.
Optional: Notify me when opened sends you a notification when someone opens the item, including anonymous visitors. At most once per visitor per day.
For a document, pick a saved version in the list and press Publish next to it. A public document shows that version, not your live draft. If the current text is not saved, press Save and publish. If no version exists you see No versions saved yet. Save a version first to publish it.
For a data table, dashboard, site or form, press Publish in the switch row. These show the live state, not a snapshot.
Use Copy link for the address, or Open published version to see it.
What each type exposes
Type | What anonymous visitors get | What to check first |
|---|---|---|
Document | The version you published | Translations. If a language is missing you see Translations missing — cannot publish with the list |
Data table | Every readable column of every row, including image and file addresses | Column visibility. The dialog warns: close columns you do not want exposed first. Publishing is refused if no column is shared with anonymous visitors |
Dashboard | Panels, only where their source is cleared | |
Form | A page that writes a row into the target table | The pre-flight list of tables the form's pickers need (below) |
Site | The shop or booking site | Publishing the item is not enough. See section 2 |
Careful: publishing a data table makes all of its rows readable by anyone with the link. There is no per-visitor row filtering on the public side. The dialog says so for forms' reference tables as well.
Forms: the tables behind the pickers
A form's reference fields let a visitor pick a record from another table, and that read is anonymous. The dialog lists these tables under Tables this form needs published. Tick the ones to publish with the form, then use Publish selected. A table you leave unpublished makes its field show Could not load this table. A table that holds this form's own submissions is left unpublished on purpose.
A listed form also shows a Public form URL and, if you may call it from your own website, a Submit endpoint (API). For a browser on another domain to use the endpoint, its address must be in the allowed origins. Treat each entry as a trust grant; see .
For forms in general (consent, captcha, review), see .
2. Put a shop or booking site on the web
A site is a public shop (bound to a catalogue table) or a booking page (bound to a bookings table). Create one with New storefront in the navigator, or install the Online store (website) or Booking website module. The editor is titled Storefront setup or Booking site setup.
Going live is a deployment, not a switch. Publishing the site item and the space is necessary but not enough.
Open the site. If a yellow box says Customers can't see this storefront yet, press Publish required documents. It publishes the space, the site page and the catalogue tables the site reads.
Footer content pages are versioned documents, so they are not published for you. The box lists them with a Publish button each.
Open the Content tab and find Publish to web.
If there is more than one template, pick one under Template.
Under Default address, check the address shown and press Publish. The site is then served on its own address.
For your own domain, enter it under Custom domains (for example shop.example.com) and press Add domain. If the status is not live, add the DNS record shown, then press Recheck. A self-hosted row is live at once and shows Point your domain here.
With more than one live address, choose which is the primary address with Make primary. Login links, notifications and the public page point at it.
After you republish a document, Update caches purges the shop's cached pages. Without it, changes appear within about a minute.
Other controls in the editor: General (site type, Site icon, contact channels shown in the header, languages), Catalog and Commerce for shops, Booking for booking sites. Unpublish and Remove take an address down.
Payments for a shop are a separate setup. See .
For the operator's side, see storefront template deploy.
3. Branding
Open a site and press Brand & theme. The dialog sets colours (Palette presets, Colours, + Advanced colours), Heading font, Body font, Corner radius and Logo, with a Live preview and contrast warnings. The theme is shared by the whole space, not one site. It applies to the app and to the space's public pages.
Press Save branding to apply it. Reset to default returns to the built-in theme. Opened from a storefront, the dialog also shows the shop's own palette, which is saved with the site's Save button, not the dialog's.
Branding can only be reached from a site's editor. There is no separate menu item.
4. Customer portal start pages
The portal is a separate sign-in site. Its landing pages are set in External Portals, tab Start pages. That is portal setup, not public publishing; see and .
5. Asset Library
Open Asset Library from the space menu. It is one catalogue of the images and files your tables, sites and documents use.
Press Upload and choose files. Search by filename or group; type #tag to filter by tag.
Click an asset to open its Details: Filename, Alt text, Photographer, Rights holder, License, Expiry (YYYY-MM-DD), Tags (comma-separated). Press Save.
Open Used by to see which rows reference the asset.
Use Select, then Make a group, to group related images as variants (for example by colour). Variants let a row keep showing the right image after group edits.
Unused shows assets that no table row references. You can select and Delete them in bulk.
Scan expiry checks every asset for expired rights and raises an automation event for each newly expired one.
Anyone with Read can browse. Upload, edit, delete and scan need Edit.
Needs your administrator: uploads are stored in the installation's file storage. If an upload fails with a storage error, ask your administrator to check it. See .
Files uploaded to the Asset Library, and images pasted into documents, are not private. Their address (/api/files/...) opens for anyone who has it, with no sign-in, whether or not the page that shows them is published. The address contains a long random name that cannot be guessed, but anyone you give it to, or who sees it on a page, can keep using it. Do not upload anything confidential as an asset or a document image. Files attached to table rows or documents (file cells and attachments) are different: they open only for signed-in people with Read on the space, for portal users who can see that row, or for anyone viewing a published document, table, site or whiteboard that shows them. A published form never makes its submitted files public.
6. The demo guest link
A space marked as a Demo space can also have a One-click guest link: anyone opening /demo/<alias> is signed in as a shared read-only guest, with no AI chat. This is for showcase spaces on a landing site. The switch is not an owner setting. Only a platform administrator sees it, so ordinary spaces do not have one.
How to check it worked
Open the link in a private window, not signed in. You should see the public page, not a sign-in screen or Project not found.
For a site, open the address from Default address in a private window.
For a dashboard, look for panels that say Not available; see chapter 10.
Check Edit, then Published on the space to see the space switch (Visible in public portal or Hidden from public portal).
Undo / what can go wrong
Unpublish takes the item offline. A document keeps its share token, so a re-publish gives the same direct link.
To make the whole space private, turn Published off in Edit. Unpublishing items does not do this.
A data table published by mistake is the worst case: its rows were readable until you unpublished. Treat any data that was exposed as seen.
"Published, but 404": the space switch was off, or a site has no live deployment.
Branding is shared, so a change affects every site and public page in the space.