Skip to content

Finding your way around the admin

The sidebar is assembled per role rather than per site, and there’s no top-level Content item — Site Tree is where every page is actually reached from.

What the sidebar shows you comes from your role, checked once per row — not from the site you’re currently working in. Which SITE you’re on changes what’s inside a surface: which pages are in the tree, which items are in a list. It never changes which surfaces you can see at all. Keeping those two questions apart saves a lot of “why can’t I find this” detours.

The sidebar is a role filter, not a map of the site

Every row is checked against your role before it’s drawn, and a group heading itself disappears the moment none of its rows survive that check — so a colleague on a lower role isn’t looking at a greyed-out version of your sidebar, they’re looking at a shorter one. If something is missing from the sidebar entirely, that’s a role question. If a specific page won’t show up inside a surface you can already see, it isn’t — read on.

There’s no Content item — Site Tree is the door

There’s no top-level “Content” entry in the sidebar; every content surface is deliberately left off it. Site Tree is how you reach a page to work on it — see Shaping the site tree for what its row menu can do. That’s not just a sidebar shortcut: the edit screen a row opens needs the same role as Site Tree itself, so a direct link to it doesn’t get anyone further than the sidebar already would.

A page that’s live but missing from a list

A missing page vs. a locked one

Per-page permission overrides are checked only when a specific page is opened or saved — never when a list or the tree itself is built. So a permission problem shows up as an error on a page you can already see and click into, not as a page quietly absent from a list. If a page isn’t where you expect it, that’s a listing or scheduling question; if you can see it but can’t open it, that’s a permissions one — see Content-level permission overrides.