Apps catalog and modules

agaro is modular. Each major capability, such as CRM, Invoices, Scheduling, Inventory, Marketing, or App Builder, is represented by a module. Your sidebar and available actions reflect the modules that your workspace and your user account may access.

#Open the Store

Open Store in the System group of the sidebar, or go to /modules. The catalog groups modules by business area and shows whether each module is installed, available, required, or not available on the current plan.

The areas are Sales & CRM, Website, Human Resources, Tasks and Projects, Marketing, Supply Chain, Finance, System, and Data Management. Supply Chain holds Products, Orders, Delivery, Inventory, and Purchase. Services is listed under Sales & CRM, and Projects is listed under Tasks and Projects.

Use catalog search and category filters to find a capability. Selecting a module opens its details. Required platform modules appear as Required and cannot be removed.

A new self serve workspace starts with the always on pages (Dashboard, Store, Settings, and Users & Roles) and the CRM modules. Every other module is added from the Store.

#Add a module

Adding a module is one step. There is no request to send and nobody has to approve it.

1. Open the Store and find the module.
2. Select Install.
3. The module is added at once and appears in the sidebar.

Who sees what on a module card:

The same people can remove a module. The server checks your role again on every install and removal.

The Store no longer offers Request access. Requests that were still open when direct install began are closed as approved when the module is installed.

#Modules that need Inventory

Delivery and Purchase are modules of their own, and each works with Inventory. If Inventory is not installed, the card says that the module works with Inventory and asks you to add Inventory too, so its pages open. A sales order needs both Orders and Inventory.

When Delivery and Purchase became separate modules, they were installed in every workspace that already used them as part of Inventory, and everyone who had Inventory access kept the same access to them.

Inventory keeps its Warehouse, Quality, Barcode, and Maintenance apps as menu switches in Inventory settings. Their cards show those apps and link to Open Inventory settings. See Inventory control center.

#The Brand new module announcement

A new module is never installed for you. It appears in the Store, and the people who can add apps see one centered dialog titled Brand new module, check it out. It names the module and describes it in one line.

• Check it out opens that module's details in the Store.
• Not now closes the dialog.

Each person is asked once per module, in any workspace. Only one announcement shows at a time, and the next waits for a later visit. A module is announced only while it is new, only to a workspace that does not have it installed, and never while someone is acting as another person. The current announcements are Delivery, Loans, Documents, and Probation.

#Plan and add on requirements

A module card can say that the module needs a higher plan or a paid add on.

• Included in the plan: a person who can add apps sees the plan that includes it and an upgrade button. Other people see that an admin can upgrade the plan.
• Paid add on: the card names the add on and offers Purchase to someone who can manage billing. Other people see that an admin can purchase it. App and Website Builder is an example. Billing status remains the authority, and installing a compatibility key does not bypass it. See Plans.
• Contact sales: a sales led module is arranged with the Agaro team.
• Not available: a module that is retired for new installs, or that no plan offers yet, says so and has no button.

#Installed does not always mean usable

Access is resolved from several controls together:

1. The module must be installed or granted to the workspace.
2. The plan or paid add on entitlement must be active.
3. The signed in user must have app access through their role, access group, or explicit user module access.
4. The workspace subscription must permit the requested operation.

This is why one teammate can see a module that another teammate cannot, even inside the same workspace. Ask a workspace admin to review Roles and Settings → Security → Access Rights when the workspace has the module but your account does not see it.

#Remove a module

A Super Admin, Developer, or Manager can remove an optional module from the Store. The module leaves the sidebar. Required modules cannot be removed.

Removing a module is not the same as deleting every business record it produced. Do not treat removal as a data erasure workflow. Use the module's own trash or retention controls, or a formal workspace data request, when records must be removed.

#Troubleshooting

#The card says an admin can add this app

Your role cannot add apps. Ask a Super Admin or Manager to install it.

#The module says purchase required even though it appears installed

The installation row and the paid billing entitlement are separate. Open Settings → Plan and Billing and verify that the relevant add on is active.

#The Install button is missing

Read the status text on the card. Common reasons are a plan requirement, a paid add on requirement, a read only workspace, a retired module, or a role that may browse but not add apps.

#A teammate cannot see an installed module

Check their role, app access, access groups, and explicit module grants. Employees and viewers can have a narrower app set than admins and managers.

#Delivery or Purchase pages will not open

These modules need Inventory as well as their own module. Add Inventory from the Store.

#Where is Manufacturing?

Manufacturing is not currently offered, so there is no Store card for it, and it is not in the sidebar. See Bills of materials and work centers.