Skip to main content
Outcome: a Company vault with an index, a useful procedure, searchable source material, and deliberate reader/editor roles. You need: a workspace owner or Company vault admin. Inviting colleagues requires an appropriate plan and available seats.

​
1. Start with a structure

If Company is empty, apply Northern Logic Wiki. Read SCHEMA.md and index.md before adding folders. Use Templates to build a larger reusable structure when needed; do not apply a whole template over existing knowledge. For an existing populated vault, organize it incrementally. Begin with a clear index rather than moving every file at once.

​
2. Write one procedure people actually need

Create a page such as client-meeting.md. Include:
Save it and link it from the index using a relative Markdown link or wikilink. Open the link to verify it.

​
3. Add supporting material

Import existing Markdown into sources/ or use Convert for a supported public source. Review the resulting text and link the relevant source from the procedure. Do not treat an unreviewed extraction as an approved policy.

​
4. Assign access

Invite readers through Team. Grant Editor access only to the people or groups responsible for maintaining the handbook. Use a separate team vault for material requiring different membership.

​
5. Make it findable and maintainable

Search for “client meeting” and open the result. Check Activity to see the saved revisions. If your agent will maintain the wiki, copy the skills setup prompt and verify its schedule in the harness that will run it. Check your result: a teammate can open the index, find the procedure in Search, and read it with their intended role. A paired tool sees the same saved Markdown after sync catches up.

​
If it did not work

If a teammate cannot open the index or linked source, review their vault permissions. If applying a template fails because the vault already contains files, keep those files and organize the wiki incrementally. Next: Knowledge maintenance.