Site details & error pages
Set your system email and point your front page, 404, and 403 slots at pages you've built — from the Globals studio
The Globals studio's Site tab is where your site stops being anonymous — you set the address system mail comes from, and you choose which pages serve at the site root and when something goes wrong.
Open the Site tab
From the top nav, open the Site menu, choose Globals, then switch to the Site tab. You'll find the system email field and the three page slots.
System email
Set the address system mail is sent from — password resets, account notices, and other notifications. This is the "from" identity your visitors see on those messages.
Front page, 404, and 403
Point each slot at a page you've already built:
Front page
The page that serves at your site root — the first thing visitors see.
404 — not found
Shown when someone hits a URL that doesn't exist.
403 — access denied
Shown when someone tries to reach a page they're not allowed to see.
Pick any published page from the same picker used everywhere else in the console — for example, Fernway Botanical Studio's welcome page for the front page slot. If you'd rather, paste a token like entity:node:<id> instead.
Every field is optional
Each slot falls back gracefully:
- An empty field means "use the shipped default."
- Clearing a field puts the default back.
- Deleting a page that a slot points at safely resets that slot — no broken site root, no dead error page.
What happens on publish
The agent never publishes on its own. Your changes live in an unsaved draft until you press Publish — only then do they take effect.
On Publish, the choice takes effect immediately. Your chosen page serves at the site root, and visitors who hit a missing or restricted URL see your page — styled in your brand — instead of a bare system error.
Tip
Build a friendly 404 that links back to your best pages. A lost visitor on Fernway Botanical Studio's site is one plant guide away from staying.