Skip to main content

Modules

A module is a feature you switch on for a workspace. It's the unit Cobblr is built from. You enable the ones you want and ignore the rest.

The features you turn on​

The modules you actually manage are the ones you switch on for what you're tracking: Inventory, Tasks, Machines, Calendar. Enable one and it adds its area to the app, along with its fields and some default views.

A few foundational modules are always on, and you can't turn them off: things like file storage, locations, and notifications. They quietly back everything else, so each module you enable gets them for free.

Enabling a module​

Modules are enabled per workspace. Two workspaces on the same instance can be completely different apps. Turn a module on and its features appear right away. Turn it off and they go away again, without touching your data or the other modules.

What a module brings​

When you enable a module it can add:

  • a place: a nav entry and its own screens
  • fields: the attributes its items carry, which you can extend with your own
  • views: sensible default lenses (a table, a kanban) that you can customize
  • behaviors: how a scanned barcode gets routed, say, or how a machine reports status

Instances: more than one copy of a module​

A single module can appear more than once, skinned for a specific purpose. The Machines module can provide a 3D Printers area, a Lasers area, and a CNC area, each with its own name, nav entry, and custom fields that fit it, while the items underneath are still just machines. That's how Cobblr gives you a focused, purpose-named section without forking the module. (More in Instances.)

You don't usually assemble modules by hand from an empty workspace. You start from a Bundle, which is a ready-made set of them.