Documentation
Written from what the software does, not from what would be good to say about it. Every capability described in these pages is one the product claims for itself — the guides explain, order and warn about them, and add nothing.
User documentation
The reference, module by module. All 43 modules across 9 categories: what each is for, what has to be in place before it is useful, every task it does, and what it hands to the rest of the suite.
43 modules · 189 tasks
Open it In preparationUser guide
Not a module at a time but a business at a time: getting an installation running, the first week, who should be given what, and how a record travels from an enquiry to a paid invoice.
Six chapters
What it covers In preparationDeveloper documentation
For the people integrating with it: the module layout, how an app is switched on and what it declares it depends on, the permission model, and the routes an authorised caller can reach.
2,644 routes
What it covers Not released yetDesktop app
WorkSuite in a native window on macOS, Windows and Linux — mail, chat, calendar, tasks, files, CRM and HR, with notifications from the system tray.
Version 0.2.14
What it coversEvery module, by category
The user documentation is organised the way the suite is. If you know which app you are in, start here.
Sales
Finance
Supply Chain
Human Resources
Services
Websites
Communication
Productivity
Administration
What these guides will not do
They will not walk you through an interface screen by screen. Buttons move, screens get redesigned, and a manual written against them is wrong at the next release while still sounding authoritative. What is written here instead — what a task is for, what has to exist first, what it changes elsewhere, and what usually goes wrong — is the part that survives, and the part people actually open a manual for.