Your company's knowledge – finally where the work happens.
Structured knowledge spaces, tightly woven into projects, tasks and risks. No second tool, no second login – and no more docs where nobody knows if they still hold true.
Engineering knowledge space
OrganizationDeployment runbook
Verifiedupdated 2 hrs ago
Linked
The knowledge exists – it just can't be found.
Documentation gets created everywhere. But the moment it's needed, the hunt begins. Sound familiar?
Scattered across ten places
A bit in Confluence, a bit on a shared drive, the rest buried in chat threads and people's heads.
"Is this still current?"
Nobody knows whether the page from two years ago still holds – so no one trusts it.
Knowledge walks out the door
The one person who knows the system resigns – and takes half the documentation with them.
No link to the work
Docs sit detached next to projects and tasks instead of right on them.
From scattered notes to living knowledge
WORKSPACE.PM guides your knowledge through a cycle that structures it, links it – and keeps it current.
Structure
Spaces for the organization, projects and teams with nested pages.
Capture
Rich-text editor and templates – from blank page to finished page in minutes.
Link
Connect pages to projects, tasks and risks – with backlinks.
Keep current
Verification and version history make the content something you can trust.
Structure & Hierarchy
A home for every piece of knowledge – without the chaos
Create spaces for the whole organization, individual projects or teams. Within a space you nest pages as deep as you like – and find everything again through a collapsible tree navigation.
- Spaces for organization, project and team
- Arbitrarily deep nested pages with readable links
- Pin, archive instead of delete, restore
- Unique space names with clear duplicate protection
Knowledge spaces
Architecture decision: API gateway
Why not Kong as an alternative?
OpenCapture & Collaborate
Document like in your word processor
A comfortable rich-text editor with images and file attachments – no markup knowledge required. Turn recurring formats into templates once. And feedback stays right on the relevant passage.
- Rich-text editor with image embedding and file attachments
- Reusable templates: decision, onboarding, retrospective …
- Inline comments anchored to the highlighted passage
- Labels to categorize and filter thematically
Links & Backlinks
Knowledge that surfaces exactly where you work
This is the difference from a separate wiki tool: every page can be connected to projects, tasks, risks, meetings and more. And the backlink appears automatically on the record – so you instantly see which docs exist for a project or risk.
- Link to nine entity types – project, task, risk, meeting …
- Automatic backlinks on the linked record
- Two-step wizard: pick type, search target – no copying IDs
- Never ask again where the docs for this item live
Payment gateway (ADR-014)
Architecture · verified
Referenced by
Project structure
Documentation
Docs on the Project Structure
Documentation on the work package – not beside it
Attach knowledge directly to a work package in the work breakdown structure. Higher-level documentation is automatically visible at deeper levels without double maintenance – and the project lead sees the docs for the entire sub-structure at a glance.
- Docs panel right on every work package
- Inherited pages from parent packages – no double maintenance
- Docs from sub-packages for the full overview
- Inherited content read-only, with a jump to the original
Always Current & Traceable
Documentation you can finally trust
Reviewed pages carry a verified badge with a due date – once the interval lapses, the system automatically prompts for a re-check. Every change is versioned, and a report shows owners instantly which content is overdue.
- Verified badge with automatic expiry date
- Editing resets verification automatically
- Verification report with live counters per status
- Automatic version history – every revision restorable
Verification overview
42
All
31
Verified
6
Expired
5
Unverified
Version history
Permission level
No access
Read
Edit
Admin
Visibility per space
Permissions & Confidentiality
You decide who sees what
A four-level permission model controls reading, editing and administration. On top of that, project and team knowledge stays limited to the people involved – while PMO and administration keep full oversight at all times.
- Four levels: no access, read, edit, admin
- Scope confidentiality: project/team knowledge stays internal
- PMO override: admins see all spaces
- Every wiki change in the central audit log
AI & Automation
Ask questions instead of searching pages
The built-in AI assistant answers questions straight from your documentation – and names the source. And because every wiki activity raises events, you can hook notifications and workflows onto it.
- AI answers questions from the wiki – with source citation
- Summaries and quotes from specific pages
- Workflow triggers on new or changed pages
- Full REST access to all wiki content
In three steps: enable the feature flag, start the canary rollout, check the metrics. Details in the runbook.
Source: Deployment runbookA wiki that doesn't feel like a second job
The most common reason knowledge management fails: it feels like extra work. Not with WORKSPACE.PM.
No second tool
Knowledge lives next to tasks, projects and reports – in the same permission world, without a second login.
Templates, not a blank page
Recurring formats come pre-built. You fill in instead of starting from scratch every time.
It reminds you
When a page's verification lapses, the system speaks up on its own – you don't have to remember.
A protected help area for everyone – without mishaps
Alongside internal project knowledge, you maintain an organization-wide, read-only help area: central, editorially curated answers for all users – without anyone accidentally changing something. Internal knowledge becomes lived self-service.
Frequently Asked Questions
Wiki & Knowledge Management
For project-related knowledge: yes. Content sits right next to tasks, projects and reports – in the same permission world, without a second login. The decisive advantage is backlinks: on every project or risk you instantly see which docs relate to it.
A four-level permission model (no access, read, edit, admin) controls the rights. On top of that, project and team knowledge stays limited to the people involved via its scope – enforced centrally on every access.
Pages can be verified and get an expiry date. Once it lapses, the content automatically counts as due for review again, and a report shows owners all overdue pages. Every edit resets verification so changed content isn't falsely treated as reviewed.
Yes. Templates for decisions, architecture, onboarding, retrospectives, processes and meeting notes can be created and picked when creating a page. Any good page can also be saved as a new template.
No – you can start small. Create new pages directly and bring existing knowledge over gradually. Many teams start with the most important runbooks and onboarding pages per project.
Make knowledge findable – before someone takes it with them.
Try WORKSPACE.PM free for 14 days and experience documentation that lives right next to project work – structured, linked and current.