Apps & install

How installing an app adds menus, screens and permission groups.

The Apps screen

Apps lists every module available on the server's addons_path. Installing an app brings its menus, screens and permission groups into the database.

What install does

• Creates or updates tables for the app's models
• Loads views, menus and access rules
• Loads seed data declared in the manifest
• Respects depends so prerequisites install first

Engineers can also install from the CLI with -i (see First boot). Operators use Apps for day-to-day enablement once the system is running.

A sensible order

For the lead-to-cash path that works today, enable (or ask an engineer to install): contacts, product, crm, sale, sale_crm, account. Add purchase and hr only if you need them.

Where to see what ships

The product Addons page lists modules and status (working / partial / placeholder). Prefer that catalogue over guessing from Apps alone while the product is pre-alpha.

Next step

Continue with Lead-to-cash.

What not to do

• Do not enable placeholder apps expecting finished workflows.
• For a full dev install, operators can use -i all instead of listing every module.

Sumeru is pre-alpha (no tagged release, no upgrades). Part of Project Meru.