Spaces and pages
Organising Vault, and the three space roles that control who can read and write.
Spaces
A space is a team-scoped container of pages. Think one per area of concern: Engineering, Product decisions, Runbooks.
On the Vault home you see the spaces you can access. n creates a space; v toggles between grid and list.
Most teams need fewer spaces than they first create. Nesting inside a space is free; a space is a permission boundary, so create one when a different group of people should see something, not when a different topic starts.
Pages
Inside a space, n creates a page. Pages nest as deep as you like, and each has its own URL.
A page’s URL is stable and deep-linkable — from an issue description, a comment, or another page. Links from issues can add an eligible page’s title and link to a context bundle. The page body is not copied; the reader still needs authorized access to open it.
Referenced by
A page’s Referenced by panel lists issues whose descriptions or loaded comments cite that page, with links back to the issues. Backlinks are derived from available active-team data; an unloaded discussion may not appear yet. An empty panel is not proof that no one has referenced the page elsewhere.
Space roles
Access is per space, on top of team membership. Being in the team does not by itself grant access to every space.
| Role | Can |
|---|---|
| Viewer | Read pages in the space. |
| Editor | Read and write pages, create and delete them. |
| Admin | Everything an editor can, plus manage the space’s members and roles. |
A space can be open to the whole team, restricted to named members, or effectively private with one admin.
Space access and the context bundle
The external bundle excludes enrichment from restricted/private spaces even when the copier can read them. Unknown space visibility also fails closed. It includes an exclusion notice rather than adding the page title, space, metadata or source row. Verbatim user-authored text can still contain a URL to a restricted page; it is not redacted. A clipboard document cannot enforce the eventual recipient’s membership. Only team-visible references are enriched, and the current bundle does not include Vault page bodies.
Deleting
Deleting a page deletes its children. Deleting a space deletes everything in it. Neither is a soft delete and there is no trash.
Individual pages have version history you can restore from — but that is history of a page, and it does not survive the page being deleted.
Related
- Editing and collaboration
- Members and roles — the team-level roles these sit on top of.
Something here wrong, missing or out of date? Tell us at support@orneos.com — corrections to these pages are welcome and we would rather hear it than have you work around it.