Skip to main content
Outcome: one useful shared procedure, a clear access structure, and a teammate who can find it. Before you start: you need workspace Owner or Admin access for team administration. New workspace owners first complete account and workspace setup. Team membership and team vaults require a plan that supports them; check your plan.
1

Choose one first use case

Start with a procedure people ask about repeatedly: client onboarding, meeting preparation, or a team handbook. Name one person responsible for keeping it accurate.
2

Choose the access boundary

Use Company for broadly shared knowledge. Use a team vault when membership needs to differ, and folders for topics with the same audience. Review vault access before placing sensitive material.
3

Choose a starting structure

An empty vault can receive a wiki template. Apply it before adding files. If your vault already contains knowledge, organize it deliberately; do not delete existing content merely to apply a template.
4

Write one useful page

Follow Build a company wiki. Include when to use the procedure, its owner, steps, and links to supporting sources. Verify the page appears in Search.
5

Invite and verify

Invite your teammate, grant the required vault role, and send them Join your team. Have them open the page using their own account. Your administrator view cannot prove their access.

​
Check your result

Your teammate can find the procedure and knows whom to ask about it. If they need to contribute, they can save a small agreed edit and you can inspect it in Activity.

​
Keep the rollout small

Expand after the first workflow is useful. Add department vaults when access needs justify them. Use Keep knowledge useful to establish a review habit, and Employee onboarding for later teammates. If it did not work: review editing access or accounts and invitations.