Organising across spaces

A workspace often grows to dozens of Spaces. Keep that list navigable by making each Space's audience and purpose obvious.

Name Spaces so they sort themselves#

• Use stable team or function prefixes where scanning matters: eng-platform, eng-web, sales-enterprise.
• Name project Spaces after the outcome, not a temporary meeting.
• Distinguish public and private variants clearly rather than relying on memory.

Renaming is cheap. If people repeatedly open the wrong Space, fix the name.

Prefer public unless the work is genuinely restricted#

Public Spaces are discoverable and let knowledge spread without invitation churn. Use private Spaces for security, personnel, legal, customer-confidential, or small pre-launch work. Starting open is usually easier than copying a private conversation into a new public Space later.

Share one conversation across Spaces#

Crossposting places the same message thread into several Spaces. Replies and reactions stay unified because there is one conversation with multiple placements. Use this for a release decision shared by engineering and support, or an incident thread visible to both the owning team and an incident room.

Avoid crossposting every message. If two audiences need all the same work, they probably need one shared Space.

Link durable Canvas context#

Canvas documents and databases are top-level workspace resources. Mention or paste their direct link into any Space instead of copying their content. A Space-audience Canvas grant can give that Space's readers access, but it does not place the Canvas inside the Space.

Archive old Spaces#

Archive completed project or incident Spaces. They disappear from active navigation and become read-only while preserving messages, threads, files, and links. Authorized members can still open them directly, and eligible members can reopen them when work resumes.

See also#

• Spaces → Overview for public/private behavior.
• Spaces → Organising a space for feed and thread habits.
• Canvas documents / Canvas databases → Sharing for direct links and Canvas access.