Answers stay out of the chat archive
Every guide has a home. Share a link to the current version and use search to find the right detail.
A Netori product
Answers for your team. Help for your customers.
Publish guides, documentation and answers to common questions. Open your knowledge base to customers or create private sections for your team, all in one place with your branding.
Installation on one prepared server, logo and colours, up to 5 sections and 3 access groups, plus editor training. Server costs, writing, content migration, custom features and support are separate.
One-time setup work. Final scope and quote agreed before starting.
Netori Wiki / Features
Find an answer, update a guide or check acknowledgements — a dedicated view for each task.
An editor with formatting, templates and attachments. Publication, section and access settings sit alongside it.
Views, reading time, group reach and read acknowledgements. The screen shows example data, not client results.
Your company, your brand
We tailor Netori Wiki to your company: your logo, name and colours, with knowledge sections and employee access configured for your team. Branding can also be updated after launch.
Try a colour and enter your company name.
Guides, answers and training in one place.
Open →Branding example with fictional content. Your logo replaces the initial.
Every guide has a home. Share a link to the current version and use search to find the right detail.
Publish product guides, common questions and usage examples. Share links without requiring registration.
Turn individual experience into a shared resource that your team can improve and pass on.
Features
Articles, videos, images, tables and downloadable files. Nested sections keep everything organised by topic.
Search article text and the contents of supported document attachments. Bookmark frequently used materials.
Create content without a developer. Import Word documents, paste screenshots and start with guide, policy and checklist templates.
Publish guides for customers without requiring sign-in. Keep internal content limited to signed-in users or selected groups. Set editing permissions separately.
Mark important materials as required. Employees acknowledge reading them and managers can see the record in a report.
See which articles people read, which remain unopened and which searches return no results. Export reports as CSV.
We deploy a separate knowledge base for your company on your server or chosen hosting. We configure your name, logo, colours and permissions. Nextcloud sign-in can be connected when needed.
Implementation
We discuss who will use the knowledge base, where your documents live and which sections to launch first.
We deploy the system, apply your branding, create the structure and configure access groups.
We transfer the agreed content and show your editors how to maintain the knowledge base themselves.
The quote depends on setup, branding, document migration, permissions and integrations. After discussing your needs, we provide an itemised scope and estimate.
Hosting and ongoing support are agreed separately. We confirm the price and timeline before starting.
No. Staff with editor permissions create and update materials in a visual editor. Custom development is only needed for changes beyond the built-in features.
Yes. Word import and pasting with tables and lists are supported. We agree the migration volume and formatting review before implementation.
No. Sections and articles can be public, available to signed-in users or limited to selected groups. Editor permissions are configured separately.
Yes. The knowledge base works in a browser and adapts to mobile screens. No separate app is required.
Wiki focuses on knowledge: guides, policies, training and read acknowledgements. Netori Office brings together chat, files, mail and CRM. The knowledge base can be deployed independently.
Netori Wiki
Tell us who the knowledge base is for: customers, your team or both. We will propose a structure, access rules and an implementation plan.
Discuss a rollout ↗