Start with a purpose
Think of a workspace as a shared area governed by an organization’s membership and access rules. Within it, teams can organize conversations around projects, departments, or recurring work, depending on the service. An account and a workspace are not the same thing.
Build a structure people can navigate
Choose names that explain the work rather than internal jokes. A project space might contain its owner, current goal, and a link to the decision record. Keep announcements separate from discussions if that helps people find the information they need.
Set boundaries early
Decide who can invite members, which information can be shared, and how old spaces are handled. For sensitive work, confirm privacy and retention settings with an administrator; do not infer access rules from a channel name alone.
A starting structure that can grow
For a small product launch, create only the spaces needed for the work: a shared launch discussion, a place for decisions, and an announcements route if needed. State the purpose and owner of each. If external partners join, verify their visibility before sharing a document. After the launch, decide which conversations should remain discoverable and which can be archived under the organization’s policy. Do not create a new space for every one-off question.
Choose the next step
| Situation | What to check |
|---|---|
| People cannot find decisions | Add a short decision summary and link to the durable record. |
| A project has ended | Review ownership, retention, and archive settings. |
| Membership changes | Check access to both the workspace and individual spaces. |
A practical checklist
- Name the workspace and identify an owner.
- Create a small number of purposeful spaces.
- Explain membership and sharing rules.
- Review inactive spaces and access regularly.