Modules

A module is a type of data at the top of the Boost.space data model — the tables of your database. Boost.space is modular: you build the modules you need and add more as you grow. Each module is a database of records, organized into spaces and described by fields.

Build the modules you need

Modules are fully customizable — define a module's name, icon, spaces, key field, permissions, and fields to match your exact process. You can also generate fields with AI while building a module.

See Create a module for the step-by-step.

Modules interconnect automatically

Modules connect to each other out of the box, so data flows between them without manual setup — for example, a won opportunity can create a follow-up order in another module.

Build on custom modules

Start every new project from a custom module you design yourself. That is where the work has gone and where it keeps going: you define the fields, the structure, and the behaviour, so the module fits the data instead of the data being bent to fit the module.

The classic named modules — Tasks, Contacts, Products, Invoices, Warehouses — came from an earlier generation of Boost.space, when each one was pre-designed for you. Custom modules now cover what they did and more, so the classic ones are not the place to begin something new. They are documented in the legacy documentation for the systems still on them.

One module, one kind of data

Give each kind of data its own module, and use spaces for variations of the same kind. A module has a view across all of its spaces at once, and that view unions the fields of every space beneath it — so spaces holding similar records produce a readable overview, while unrelated records crammed into one module produce a very wide table of mostly empty columns. See Spaces overview for the longer version.

Admins manage modules

System administrators create and configure modules, then make them available to other users. For per-module configuration, see Individual modules – setup (admin).

Learn more

Looking for the classic named modules (Tasks, Contacts, Invoices, Products…) or their setup? Those are documented in the legacy documentation.