Modules

A module is one licensable admin area, keyed on a code that four things share: a navigation requirement, a settings scope, a chat tool group, and a plan entitlement. Core modules are linked to every project at provisioning; the rest are switched on per project. Each module's page states what it owns, its routes, its settings scope, its chat tools, and what a tenant loses when it is switched off.

Commerce

Module	Core	Owns
`marketing`	✔	The always-on public site: home, services and the enquiry form.
`products`	✔	Catalog, prices, stock, collections and option axes.
`orders`		Quotes, sales, invoices, credit notes and payments.
`deliveries`		Dispatch, tracking and partial deliveries.
`storefront`		The public buy-side: browsing, cart, checkout and customer order history.

People

Module	Core	Owns
`identity`	✔	Persons, user accounts and role assignments.
`organizations`	✔	Customers, suppliers and the locations they trade from.
`employees`		Employment, shift templates, rosters, leave and attendance.

Performance

Module	Core	Owns
`analytics`	✔	Rollups over orders, order lines, deliveries and visits.
`sales-performance`		Targets, actuals, commission plans and the attainment KPIs over them.

Operations and field

Module	Core	Owns
`surveys`	✔	Authored surveys, quizzes and checklists, and the responses to them.
`visits`		Visit plans, visits and the proof captured against them.

Configuration

Module	Core	Owns
`references`	✔	Lookup types, lookups and their statuses.
`settings`	✔	Tenant behaviour: grid settings, form surfaces and application config.
`messages`	✔	Tenant copy overrides, namespace by namespace.
`branding`	✔	Theme tokens and brand imagery for the storefront and admin.
`files`	✔	The tenant file library, its folders and its sharing model.

Oversight

Module	Core	Owns
`audit`	✔	Change history and the capture runs that wrote records.
`notifications`	✔	Notifications, confirmations and push tokens.
`incidents`	✔	The queue of failures and deviations a person must look at.

Modules

The module catalog — one page per module code.

Commerce

Module	Core	Owns
`marketing`	✔	The always-on public site: home, services and the enquiry form.
`products`	✔	Catalog, prices, stock, collections and option axes.
`orders`		Quotes, sales, invoices, credit notes and payments.
`deliveries`		Dispatch, tracking and partial deliveries.
`storefront`		The public buy-side: browsing, cart, checkout and customer order history.

People

Module	Core	Owns
`identity`	✔	Persons, user accounts and role assignments.
`organizations`	✔	Customers, suppliers and the locations they trade from.
`employees`		Employment, shift templates, rosters, leave and attendance.

Performance

Module	Core	Owns
`analytics`	✔	Rollups over orders, order lines, deliveries and visits.
`sales-performance`		Targets, actuals, commission plans and the attainment KPIs over them.

Operations and field

Module	Core	Owns
`surveys`	✔	Authored surveys, quizzes and checklists, and the responses to them.
`visits`		Visit plans, visits and the proof captured against them.

Configuration

Module	Core	Owns
`references`	✔	Lookup types, lookups and their statuses.
`settings`	✔	Tenant behaviour: grid settings, form surfaces and application config.
`messages`	✔	Tenant copy overrides, namespace by namespace.
`branding`	✔	Theme tokens and brand imagery for the storefront and admin.
`files`	✔	The tenant file library, its folders and its sharing model.

Oversight

Module	Core	Owns
`audit`	✔	Change history and the capture runs that wrote records.
`notifications`	✔	Notifications, confirmations and push tokens.
`incidents`	✔	The queue of failures and deviations a person must look at.

Commerce

People

Performance

Operations and field

Configuration

Oversight

On this page

Modules

Commerce

People

Performance

Operations and field

Configuration

Oversight

On this page