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 Apps catalog

Open Apps from the sidebar, or go to /modules. The catalog groups modules by business area and shows whether each module is installed, available, required, awaiting approval, or commercially locked.

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

#How activation works

The button shown on a module card depends on who operates the workspace:

Submitting an access request does not mean the module is active. Return to the catalog to see whether the request is pending, approved, denied, or installed. If an approved request still shows as not installed, the platform operator must complete activation.

#Plan entitlements and paid add ons

Some capabilities depend on your plan. Workforce, full accounting depth, outreach, and the AI Assistant are examples of tier entitlements. The catalog explains the exact plan requirement when a module is unavailable.

Three module families are sold as workspace add ons:

A paid add on is separate from the base plan. Installing an old or compatibility module key does not bypass the active paid entitlement. Billing status remains the authority.

#Agency module policy

An agency admin can define module policy for all managed client workspaces under Agency → Modules. A policy can leave the platform default in place, allow clients to install, require agency approval, or block a module.

Agency policy can narrow access but cannot override a platform plan or paid add on requirement. When the platform refuses an install, agency approval cannot make it available.

#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 and Access → Access Rights when the workspace has the module but your account does not see it.

#Removing a module

Ordinary tenant users do not directly uninstall modules. A platform controlled uninstall removes the workspace installation and hides the module from normal navigation. Required modules cannot be uninstalled.

Removing access is not the same as deleting every business record produced by the module. Do not treat uninstall 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 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. Agency managed workspaces should contact their agency administrator.

#My request is still pending

The request has not been approved and activated. Agency managed workspaces are reviewed by the agency when its policy requires approval. Standard workspace requests are handled by the platform operator.

#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.

#The Install button is missing

Read the status text on the card. Common reasons are a plan requirement, a paid add on requirement, agency policy, a pending request, or a role that may browse but not request access.