Skip to main content
Outcome: a teammate can find the information needed for their first week and knows where to ask questions. Before you start: an Owner or Admin invites members. You need write access to create the onboarding page, and a vault admin must grant any additional access. Teams needs available seats, including pending invitations.

​
1. Write a first-week page

Create start-here.md in the intended shared vault. Link to real pages, rather than copying their contents into a second handbook.
Replace the descriptions with links and the partner with a real person. Keep the first reading list short enough to complete.

​
2. Invite and grant access

Invite the teammate with the intended workspace role. Review the vaults linked from the page: being able to open the index does not grant access to every destination. Use Company Viewer access for reading; grant Editor only where contribution is needed.

​
3. Test from their perspective

Send Join your team and the onboarding page location. Ask the teammate to open two linked pages using their own account and complete the small task. Fix access gaps before adding more reading.

​
4. Capture what was confusing

Have them keep personal questions or add agreed improvements where they can edit. Use Send to… for a focused review request on a page the recipient can already read. Save durable answers into Knowledge.

​
Check your result

The teammate can find a procedure, identify its owner, and explain a next action. Completing this checklist is a human onboarding practice; the app does not automatically track course completion. If it did not work: Fix editing access. Next: Keep knowledge useful.