Organize with collections

Collections organize documents and files into a navigable tree. A collection can contain nested collections, but a shallow hierarchy is usually easier for people and agents to understand.

Choose durable boundaries

Good top-level collections represent stable responsibilities, products, clients, or operating systems. Use documents for individual requirements, decisions, processes, and references within those boundaries.

Prefer names that make sense in paths. A document titled “Launch checklist” inside Products / Atlas is easier to distinguish than one inside a generic Miscellaneous collection.

Navigate and move content

Expand collections in the sidebar to browse their contents. Search when you know the concept but not the location. Moving a document or collection changes its human-readable path while preserving its stable identity.

Nested collection moves also change every descendant path. Links and webhook payloads use stable IDs alongside paths so integrations can reconcile these changes safely.

Access inheritance

Collection visibility is inherited through ancestors. A team-visible collection is available to active members. A private or selected-members rule narrows access for that collection and its descendants. The team owner retains administrative access.

Moving content can change who is allowed to access it. Review the destination collection's effective audience before moving sensitive documents or files.