Workspace and content administration
Domain focus
The Workspace and content administration domain tests how an admin configures a Notion workspace and governs content after it is created. Expect questions on workspace settings, role boundaries, page ownership and transfer, trash and restore, duplication, movement, version history, and integration controls.
Core rules
- Workspace settings live under Settings & members; the workspace owner holds ultimate control, including ownership transfer and workspace deletion. Admins manage members, groups, billing, security settings, and integrations but do not automatically gain access to every private page.
- Content lives in private pages, shared pages, or teamspaces. Teamspace pages inherit teamspace access; private pages are visible only to the creator and explicitly invited people.
- Deleting a page sends it to Trash; restore returns it to its prior location if the parent still exists. Permanent deletion is irreversible and removes page history.
- Duplicating a page copies content and subpages but not comments, permissions, or integrations. Moving a page can change inherited access, so check sharing after a move.
- Version history and workspace export are administrative recovery tools; exports do not preserve all relational behavior.
Worked example
A departing employee owns a private onboarding page and several teamspace pages. The admin should first transfer or have the employee share the private page, remove the employee from groups and teamspaces, then reassign teamspace page ownership. Removing the account alone can leave private content inaccessible. Reasoning: group removal revokes inherited access; ownership transfer preserves continuity; private pages require explicit sharing because admin role alone does not grant visibility.
Traps
Assuming admins can open all private pages; treating Trash as permanent; expecting duplication to copy permissions or comments; moving a page without rechecking inherited access.