Company Knowledge Base with Projects and Tasks
Weenvo is company knowledge base software that lives in the same product as the projects, tasks and timesheets. A knowledge base is the one place for a company’s handbook, standards and project documents. In Weenvo it is a documentation tree with access per section, a version on every edit and pages linked from the tasks and meetings they belong to.
Key benefits
Handbook above, project documents inside
The company handbook and standards sit at the top of the tree, a branch per department or practice below them, and each project’s documents inside the project next to its board. Nesting is unlimited.
Access per section
Everyone reads the handbook, a department reads its own procedures, a client reads only its workspace. Access is set per section of the tree, so public and restricted pages live in one place.
A version on every edit
Version history is the record of every change to a page, with the author and the date, and the earlier versions still openable. The version of the scope a contract was signed on is still there a year later.
Linked from tasks and meetings
A runbook opens from the request task, a brief from the content task, a proposal from the deal task. A decision recorded in a meeting points to the page it changes and the task it creates.
How a company moves its handbook and standards into Weenvo
An architecture and interior design practice with a few dozen people keeps its procedures in a shared drive, its templates in email threads and the rest in the heads of two senior partners. It moves to Weenvo in this order.
The handbook first
The office manager creates the top of the tree in Documentation: how the practice works, the project method, the client communication rules, the travel and expense policy. Each page is copied from the drive by hand and tidied on the way. The section is open to everyone in the company.
A branch per discipline
Below the handbook, the architecture, interiors and project management disciplines each get a branch: drawing standards, the review checklist, the specification templates. Access is set per section, so the finance procedures under the back-office branch are read by finance only.
Project documents inside the project
Each client project already has its board in Projects and tasks; its documents, the brief, the concept presentation, the approved drawings list, the correspondence, are kept inside the project next to the board. The client’s representative, invited into the client workspace with a limited role, reads them there.
Pages linked from the work
The review checklist opens from the review task. The brief opens from the design task. When the monthly practice meeting decides to change the drawing numbering standard, the decision is recorded in Meetings with an owner and a date, the standards page is edited, and the follow-up task to update the templates is created from the decision. The partner who reads the page a month later sees the current standard, who changed it and when.
Versions
The specification template is edited twice a year. Every edit keeps the previous version with the author and the date, so a project that started on the old template can still open it.
Search
A new engineer types the name of a supplier into search and finds the procurement procedure, the supplier page and the project where it was last used, without asking the two senior partners.
Use cases
Company handbook and policies
How the company works, open to everyone, with versions on every edit. See Weenvo for HR teams.
Standards and templates for a PMO
The project method, charter and status-report templates at the top of the tree, each project’s documents inside the project. See Weenvo for project managers.
Runbooks for a service desk
A how-to page per request type with version history, opened from the request task. See service desk in Weenvo.
Client documents in a client workspace
Brief, scope and deliverables inside the client’s workspace, read by the client contact in a limited role. See client projects in Weenvo.
What this replaces
Starting from Notion? See the Notion comparison.
One page per procedure with version history
Instead of: A shared drive with three versions of every procedure.
Documentation in the same product as the tasks and meetings
Instead of: A separate wiki next to the task tool, with a second login.
A page found by search, with who changed it and when
Instead of: "Ask the senior partner, they know".
Templates in the tree, decisions in the meeting record, linked to the page
Instead of: Templates and decisions in email threads.
Weenvo applications
Documentation
A tree with unlimited nesting, tabs, version history, access per section, attachments.
Projects and tasks
Project documents inside each project, pages linked from tasks.
Meetings
Decisions that point to the page they change and the task they create.
Company portal and workspaces
Each workspace with its own documentation for a department, a client or a contractor; one login for all Weenvo apps.
Cost
Documentation is on every plan, Free included. Documents take storage: Free has 50 MB, Standard 10 GB with 10 GB more for €6 a month. Standard is €10 per user per month with 15% off on annual billing; a practice with 30 users pays €255 a month on annual billing or €300 billed monthly. Full details on the pricing page. Last checked 2 November 2026.
Free
0 EUR per user per month
- Up to 10 users
- 50 MB storage
- Every feature
- No credit card
Standard
10 EUR per user per month
- 10 GB storage
- Every feature
- 15% off on annual billing
See Weenvo in Action
Want to see how these features work in practice? Explore how Weenvo can help your business.
FAQs
Is this a wiki?
Yes, in the sense that matters: a tree of pages with sections, tabs, version history and access per section, edited in a rich-text editor. The difference is that it sits in the same product as the tasks, timesheets and meetings, with one login.
Can documents have version history?
Yes. Every edit of a page keeps the previous version with the author and the date; an earlier version can be opened or restored.
Can access be set per section?
Yes. Each section of the tree has its own access, so the public handbook and the restricted procedures live in one tree.
Can we keep project docs inside the project?
Yes. Each project has its own documentation next to its board, in addition to the company-wide tree.
Can we import from Confluence or Notion?
Pages are copied by hand into the new tree and attachments are uploaded again; there is no automatic import. Page text, structure and attachments move; comments and page history stay in the old tool. A large wiki is moved section by section, the handbook first.
Is documentation included on the Free plan?
Yes. Up to 10 users get the full documentation module with 50 MB of storage.
Ask a Question
Specify the details of how you plan to use our solution suite or any individual product. If your organisation has unique processes and requires an Enterprise‑level implementation, you can also submit a request for a customised setup that supports more efficient workflows.
Thank you for contacting us. Our support will answer you as soon as possible!