Move company knowledge from people's heads into a knowledge base

The answer to 'How do we do this again?' often lives with just one person. When they take leave or move on, that knowledge goes with them. Subtask's knowledge base organizes procedures, handbooks, FAQs and project documentation into nested pages, all accessible through a single search box.

Create a free account Try without signing up

Unlimited users · No per-user fees · No installation required

Subtask knowledge base: document tree and troubleshooting article

Organize documents in a tree

Each document can sit under another document, creating a natural structure such as 'HR Handbook → Leave → How do I take annual leave?' The document tree on the left shows the full structure; breadcrumbs above the document take you up a level, and child documents are listed below its content.

The home page shows the 20 most recently updated documents you can access, so you can keep track of changes across the team.

An editor for readable documents

The document editor supports bold, italic and strikethrough text, three heading levels, bulleted and numbered lists, quotes, code blocks and links. Color and font selectors are deliberately left out: documents stay equally readable in light and dark themes, with a consistent layout across the team.

You can create a document with just a title and no content, which is useful for section headings such as 'Sales'.

Accent-insensitive search

A knowledge base is useful only if you can find what you need. Subtask searches titles and content, returning results with match counts, a content excerpt and highlighted matches.

People often type searches without accents. Search is therefore accent-insensitive: cafe finds a 'Café' document, and resume finds 'Résumé'. Searches require at least two characters and return only documents you have permission to read.

Who can see what?

Link a document to a workspace and, optionally, a department. Access rules are enforced on the server:

Deleting a document also deletes its children, so the server checks your permissions for every affected document.

Activity history

When the Activity History service is enabled, anyone who can read a document can open its history to see who changed it and when.

What belongs in a knowledge base?

TeamExample documents
HREmployee handbook, leave policy, onboarding checklist
Technical serviceTroubleshooting steps, machine maintenance instructions, spare part codes
SoftwareSetup guide, deployment procedure, architectural decisions
SalesPrice list notes, proposal templates, common customer questions
Quality / Health and SafetyProcedures, instructions, emergency plan

Technical service teams collect solutions to recurring faults from the help desk in the knowledge base. When a new document is published, you can notify the team with an announcement.

Knowledge base on mobile

On small screens, the document tree becomes a collapsible drawer; add, edit, history and delete actions appear in the mobile menu. Technicians in the field can open instructions on their phones.

Frequently asked questions

Is there a limit on knowledge base documents?
No. Both document and user counts are unlimited.
Does search work with accented characters?
Yes, and it also works when you type without accents: searching for 'cafe' finds 'Café'.
Can I share a document with just one team?
Yes. Link it to a workspace and people with access to that workspace can read it. Others cannot, except those with permission to view all documents.
Are document versions stored?
Change records are kept in the activity history. One-click restoration of a previous version is not yet available.
Can it replace Confluence or Notion?
Yes, for procedures, handbooks and team documents. Subtask's knowledge base shares the same user list and permissions as issue tracking, the help desk and HR.

Bring your team together in one place

Get started with Subtask for free, invite your team and create your first task in minutes. The price does not change with your user count.

Create a free account
We use cookies to improve user experience and analyze website traffic. By clicking “Accept“, you agree to our website's cookie use as described in our Cookie Policy.
error_outline Name, surname, email and message field must be valid!
error_outline Email field must be valid!
error_outline Unauthorized transaction!