# Solutions, modules, domains (/product/platform/taxonomy)



Three layers, each answering one question.

| Layer        | Answers                                             | Example                             |
| ------------ | --------------------------------------------------- | ----------------------------------- |
| **Solution** | What a customer buys                                | `commerce`, `field`, `productivity` |
| **Module**   | What a project switches on, and what a plan permits | `products`, `orders`, `storefront`  |
| **Domain**   | How modules group for a human                       | `commerce`, `people`, `oversight`   |

## Solution

A solution is a named bundle of modules: the product a customer signs up for. A **plan** is orthogonal to it; the plan prices and limits the same modules. Three solutions exist: [commerce](/solutions/commerce), [field](/solutions/field) and [productivity](/solutions/productivity).

## Module

A module is one licensable admin area, keyed on a code that four things share: a navigation requirement, a settings scope, a group of chat tools, and a plan entitlement. Two questions have two answers: is it **enabled** for this project, and does the plan **permit** it. A page or a sidebar row tagged with a module hides itself when either answer is no, and the same rule gates a typed URL, so the sidebar and the route can never disagree.

**Core** modules are linked to every project at provisioning: identity, organizations, references, settings, copy, branding, files, audit, notifications, analytics, incidents, surveys, the marketing site and products. The rest are opt-in per project.

A module code exists only for what varies between tenants. A capability everyone gets is just code; a preference one tenant sets is a settings row. Only the middle case, sold to some and withheld from others, earns a code. The assistant has no code for exactly that reason: every tenant has it.

## Domain

A domain is a grouping for people, not a gate. Nothing reads a domain to decide access; it is the axis the console lists modules along and the way permissions are grouped in the admin.

| Domain        | Holds                                                     |
| ------------- | --------------------------------------------------------- |
| Commerce      | Catalog, selling, orders and the public buy-side surface. |
| People        | Persons, user accounts, organizations and employee.       |
| Performance   | Rollups, targets, commission and the KPIs over them.      |
| Operations    | Work orders and the proof against them.                   |
| Field         | Visit plans, visits and the merchandising done on them.   |
| Configuration | References, settings, copy, branding and files.           |
| Oversight     | Notifications, audit trail, incidents and legal matters.  |