Help Center / Wiki and knowledge base /
Project wiki
Every project has its own wiki, separate from the main workspace wiki. The project wiki uses the same page editor, nesting structure, and rich text formatting, but all content is scoped to that project, so project-specific documentation stays organised alongside the work it relates to.
Creating pages in a project wiki
Pages are created from the wiki tab inside any project. The editor is identical to the main wiki editor: headings, paragraphs, bold, italic, code blocks, tables, images, links, and all other formatting options are available. Pages can be nested to build multi-level structures, so a project wiki can mirror the depth and organisation of the main wiki on a smaller, focused scale.
Access and visibility
Project wiki pages follow the project's access rules. Team members with access to the project can view and edit wiki pages, and clients with project access can view pages shared with them. Access doesn't need to be configured separately for the wiki, because the project's existing permission settings control visibility automatically.
Use cases for project wikis
Here are a few examples of what project wikis typically hold:
- Standard operating procedures for recurring workflows specific to the project
- Handoff guides documenting how to pick up the work when team members rotate
- Client resource pages with instructions, credentials, or reference material relevant to the engagement
- Meeting notes and decision logs capturing key outcomes as the project progresses
- Technical documentation covering configurations, integrations, or architecture specific to the deliverable
Project wikis vs. the main wiki
The main workspace wiki works well for organisation-wide documentation like help centres, onboarding materials, and team-wide SOPs. Project wikis handle the documentation that only matters in the context of a specific engagement, which keeps project-specific content out of the main wiki and reduces clutter as the workspace grows.
