Assignment works the same way everywhere: rules decide, thresholds refuse, overflow catches. What changes from module to module is what you would sensibly route on, and whether a cap means anything at all.
Thirty-nine modules take rules. Each has a page of its own below, with the fields worth routing on, a worked example, and an honest answer on whether caps and overflow are worth setting up there.
The groups
| Group | Modules | What routing is usually about |
|---|---|---|
| CRM | Leads, Customers, Companies, Deals, Tasks, Visits | Sharing out enquiries, and who owns the relationship afterwards. |
| Sales documents | Quotations, Sales orders, Proforma invoices, Invoices, Bills of supply, Retainer invoices, Credit notes, Delivery challans | Who is accountable for a document once it exists. |
| Purchase | Vendors, Purchase orders, Purchase bills, Debit notes, Payments made | Which buyer looks after which supplier and what is owed. |
| Inventory | Items, Stock transfers, Stock adjustments, Assemblies, Packages, Bills of materials | Who is answerable for a movement, a build or a correction. |
| Making things | Manufacturing orders, Quality inspections | Which supervisor answers for a run, and who signs for the check. |
| Delivery | Projects, Project tasks, Subscriptions, Documents, Files | Who runs the job, who does each task, who owns the renewal. |
| Money | Expenses, Payments received, Manual journals, Fixed assets | Whose spend it is, and which accountant answers for an entry. |
| After the sale | Warranties | Who handles a claim. |
| People | Circles, Project groups | Who leads a team. |
Where a cap actually earns its place
A limit per person is offered on every module, but it only means something where records arrive at a pace. These are the ones where businesses genuinely use it:
- Leads — the case it was built for, and the only module that can also cap untouched work.
- Project tasks — the clearest example of workload in the product.
- Tasks and Visits — a person can only do so many in a day.
- Quality inspections and Packages — genuine per-person throughput.
- Purchase orders and Purchase bills, where buyers are the bottleneck.
Everywhere else a cap is available and rarely wanted. A customer or a fixed asset is a relationship or a thing, not a queue.
Which modules are NOT here, and why
Some modules take no rules at all, deliberately. A warehouse, a work centre, an operation, an item category, a price list, a chart-of-accounts line, a job card, an employee record and the billing catalogue are places, steps and rows you define once — not work a person answers for. “Only mine” has no meaning on them, so they are not offered.
Two modules that behave slightly differently
| Module | What is different |
|---|---|
| Project tasks | A task is given to somebody rather than owned, so its owner is the Assigned to field. Rules set that instead of an Owner field. It is the only module in the product like this. |
| Manufacturing orders | The field is called Answerable rather than Owner. Same thing, different word, because a production run is answered for rather than owned. |
Something missing or wrong here? Tell us. A question that needed asking usually means a page that needed writing.