Who sees what in PageSpace. Every page is protected by two layers: a drive-level role that covers everyone in the workspace, and per-page grants that cover individual pages. Four flags — View, Edit, Share, Delete — describe what each person can do. View is the foundation; Edit, Share, and Delete only make sense on top of it.
Access is resolved in order, and the first answer wins.
If you're the drive owner, you can see, edit, share, and delete every page in that drive. Nothing else overrides this, and no grant can take it away.
If you're a drive admin who has accepted the invitation, you get the same full access as the owner across every page in the drive.
If you're a drive member — the default role — you start with nothing. You only see pages where someone has explicitly granted you access, or where a role template you're assigned includes those pages. Membership is the ticket to the drive; it isn't the ticket to the pages inside.
Every per-page grant is one record per person per page, with four flags. There is no inheritance. A grant on a folder does not imply anything for the pages inside it — each page is checked on its own. This is deliberate: it stops the common "I shared one subfolder and accidentally gave away the whole tree" mistake.
Role templates are a convenience layer for owners and admins. A template says "people with this role get View + Edit on this set of pages" — it saves you from wiring up the same grants by hand every time you onboard a new person. Templates don't change the resolution order; they're just a tidy way to produce the same per-page grants.
Search docs, blog posts, and more.