Gather what your company knows
in one place.

My Notes belong to you, the Wiki to your team, the Project Wiki to that project. All three use the same editor, so your habits do not change from place to place. You write without thinking about where you are writing.

Bold, italic, underline, colour, highlight, size and alignment are within reach. Press the slash key and the block menu opens, so you do not reach for the mouse. Formatting does not break the flow of writing.

You put nested checkboxes in and tick off meeting decisions inside the document. A process document doubles as a checklist. Following up on decisions does not move to a separate list.

You drag column widths, add rows and columns, merge cells and give a cell a background colour. A price list or a comparison table sits inside the document. Numbers are read inside the document itself.

You use code blocks highlighted in twenty-five languages, info, success, warning and danger callouts to catch the eye, and collapsible blocks that hide long sections. A long document stays readable with these blocks. An important warning does not get lost in the text.

Every block has a handle; you lift a paragraph, a table or a list out of its place and drop it elsewhere without cutting and pasting. Moving it does not break the formatting. Trying out a different order costs nothing.

You open a sub-document under a document and another one under that. A company handbook does not squeeze into one long page; it branches by subject. You climb down the tree to the part you need.

In a document you can mention a person, a task, a customer, a product and a date. What you mention is not a piece of text but a real record you can click. You get from the document to the work itself with one click.

You type two square brackets and link to another document. On the other side a list of "who links to this document" builds itself. The web of knowledge weaves itself as you write.

Under a document you see the pages, tasks, customers and products that link to it. Before you change a document you see who it will affect. Where a correction will land is known in advance.

From inside a task you link the relevant documents, or even open a new one from there. Whoever does the work does not go elsewhere to look for the knowledge. The guide sits beside the work.

A snapshot is taken from every editing session and the last thirty versions are kept. You open an older state, read it, and restore it if you want. A section deleted by mistake comes back.

Before you return to an older version, a snapshot of the current state is taken too. If you went back to the wrong version, you can step forward again. You move between versions freely.

If someone is working in the document, you see a warning banner. If you both write anyway, Workinno does not let one overwrite the other and asks you to refresh and carry on. Nobody's writing disappears in silence.

A document is either open to all members, or to the people, teams and projects you pick, or only to you. When you say only me, nobody sees it, administrators included. A sensitive document never opens to the wrong person.

A document you cannot see never appears in the list, in search results, in the link panel or in notifications. Not even its title leaks. Not even the existence of a document leaks.

The title and the whole text are searched; type it without accents and the accented word is still found. Typing the beginning of the word is enough, Workinno completes the rest. You find what you are after without worrying about spelling.

Anywhere in the application you open quick search, type the document's name and go straight into it. You do not walk through menus. The knowledge is two seconds away from every screen.

A new workspace arrives with company, human resources, processes, product, meetings, training, marketing, sales, development and customer relations categories in place. You do not wait to set up categories before writing the first document. The wiki starts full on day one.

Document labels come from the same pool as task labels, so the same label means the same thing in both places. You can label hundreds of documents in one go. The same idea does not split into two names in two modules.

Meeting note, project, onboarding, process, decision record, retro, post-incident review and goal tracking come ready. You do not stare at a blank page. You write the meeting note into a structure that is already there.

You turn a document you liked into a template, and your team starts from the same structure every time. Templates are managed from the settings page. The team's documents stay recognisably alike.

You drag a file onto the document or paste it straight in. The file lands in the Page Files folder of the Files module and stays among the document's attachments. The attachment is found together with the document that explains it.

You write, edit and delete comments under wiki documents. A notification goes to the document's owner and the discussion stays beside the document. The discussion does not scatter into another channel.

When your name appears in a document or someone comments on your document, a notification arrives. No notification comes from a document you cannot see. A notification never gives away a document that is closed to you.

A document stays a draft until it is ready, and you publish it when it is. You can publish several documents in one go. A half-finished document never faces the team.

You mark a document as a favourite; in the project wiki's left panel your favourites and your recently edited documents are listed separately. You do not have to search for the document you open every day. The page you use daily stays at the top.

You filter by status, category, label and author. You save the filter you use often and give it a name; drafts and published ones come ready. A crowded archive stays manageable.

You give every document a symbol and a colour. In a long list you recognise what you are after by its colour, without reading. You pick the right document without reading.

A project has its own wiki. You can also link a document that lives in the general wiki to a project and break the link later; the document is not deleted. One project's knowledge does not spill into another.

An automation rule can create a document: when a project opens, a page from a template drops into the project wiki. Opening a document and writing a comment can trigger rules too. Writing the document becomes part of the flow itself.

You ask your AI assistant and it searches your wiki and your notes. It only looks at documents you are allowed to see. You reach the knowledge you need by asking a question.

A deleted document goes to the bin together with its sub-documents and waits there for thirty days. Restoring and deleting for good are separate permissions. The decision to delete stays reversible.

The size of a document is followed with a fullness meter; it warns you as you approach the limit and asks you to split it once you pass. You never wrestle with a giant document that will not open. Documents stay a readable size.

You put a quick-note card on your dashboard; the line you write lands in a real note. You write down what came to mind without losing it. Taking a note does not mean changing pages.