Use
Modules
Turn modules on for an installation, grant them person by person, and how access levels combine.
Knotworking is a platform plus modules. The platform is always on: sign-in, workspaces, members, teams, API tokens, attachments, notifications and search. Everything else is a module, switched on for the installation and then granted person by person.
Turning modules on
KNOTWORKING_MODULES lists the modules this installation runs. The API and the MCP server read the same variable.
KNOTWORKING_MODULES=tasks,docs,time # just these
# KNOTWORKING_MODULES=all # every module, flagged ones included
# KNOTWORKING_MODULES=none # the platform alone
- Unset means every module except the flagged ones: calendar sync, accounting and dashboards are opt-in.
- An unknown id, or a module without one it depends on (
timewithouttasks), stops the API at startup, so a typo can't quietly switch something off. - Switching a module off hides its pages, data and tools. Nothing is deleted, and switching it back on restores everything, including who had access.
Access levels
In Settings, Members, Module access, an admin gives each person a level on each active module.
| Level | Means |
|---|---|
none | The module doesn't exist for this person. |
read | They can look, not change. |
write | Everything the module's ordinary pages offer. |
manage | The module's privileged actions, such as approvals and stock adjustments. |
Access rules
- Owners and admins always have manage on every active module.
- Everyone else gets their explicit grant, or the module's default: tasks, docs, time, calendar and dashboards follow the role (members write, guests read); the rest are off until granted.
- Guests never get more than read.
- A module is off for a person when a module it depends on is off for them.
- An API token has its owner's access, optionally narrowed to a list of modules. It can never widen it.
All modules
Work
| Module | Id | Depends on |
|---|---|---|
| Tasks and projects | tasks | None |
| Documents | docs | None |
| Time tracking | time | Tasks and projects |
| Calendar and meetingsflagged | calendar | None |
| Dashboardsflagged | bi | None |
| Assistant | assistant | None |
People
| Module | Id | Depends on |
|---|---|---|
| People | people | None |
| Training | training | People |
| Attendance | attendance | People |
| Workforce planning | workforce | People |
| Private HR records | workforce_hr | Workforce planning |
Operations
| Module | Id | Depends on |
|---|---|---|
| Items and suppliers | items | None |
| Recipes | recipes | Items and suppliers |
| SOPs | sops | None |
| Stock | stock | Items and suppliers |
| Demand planning | demand | Items and suppliers |
| Production | production | Recipes, Stock, Demand planning |
| Food safety records | haccp | Items and suppliers, Production |
| Quality | quality | Items and suppliers, Stock |
| Purchasing | purchasing | Items and suppliers, Stock |
| Costing | costing | Recipes, Production, Purchasing |
| Site programmes | site | Food safety records |
| Labels and nutrition | labels | Recipes |
| Specifications | specifications | Items and suppliers |
| Testing | testing | Items and suppliers, Stock |
| Product development | npd | Items and suppliers, Recipes |
| Food defence | defence | None |
| Management review | governance | None |
| Health, safety and environment | hse | Site programmes, Training |
| HSE incidents | hse_incidents | Health, safety and environment |
Sales and finance
| Module | Id | Depends on |
|---|---|---|
| Customers | customers | None |
| Sales | sales | Customers, Items and suppliers |
| Despatch | despatch | Customers, Stock |
| Accounting integrationsflagged | accounting | None |