How to Enable and Manage Add-On Modules in CrmLeaf
All editions. Core feature - no add-on required. Which modules you can enable is determined by your account's package.
Availability: All editions. Core feature - no add-on required. Which modules you can enable is determined by your account's package.
Overview
CrmLeaf ships around 40 modules, and most of them are paid add-ons. A module that is not enabled does not appear in the interface at all, so "the screen is missing" is usually a module question rather than a permission question. This article explains how packages control availability and how to enable a module for your account.
How It Works
Availability is decided in two places. The package attached to your Company decides which modules are available to it, and the module toggles decide which of those are switched on. Navigation and permissions then follow.
Package → Module available → Enable module → Permissions inserted → Menu entry appears → Configure
- Packages control what you can have. A package determines which modules are available to the Company, the seat limit for users, and the storage limit for files.
- Module availability is applied per role inside the Company, driven by that package.
- Enabling a module inserts its role permissions automatically, so the permissions to configure are present as soon as the module is active.
- Menu entries are gated. Each feature declares the conditions under which it may be shown, including whether its module is enabled, which product edition applies, and which permission is needed. A module that is not enabled cannot be surfaced by any menu layout.
- Modules seed their own defaults. When a Company is created, more than 16 modules seed their starting rows, so an enabled module usually arrives with sensible defaults.
- Some modules are edition-oriented. Construction, Solar and Manufacture pair with their editions, while Purchase, Budget, Payroll, Recruitment and Performance are used across editions.
Who Can Use This Feature?
Administrator
- Review which modules the account's package makes available.
- Enable and disable modules for the account.
- Configure the permissions and settings a newly enabled module brings.
- Watch the seat and storage limits that come with the package.
This functionality is available only to Administrators.
Prerequisites
- An active subscription or trial. New accounts receive the active trial package, 30 days by default.
- The module you want is available under your package.
- You know which roles will use the module, so you can set permission scopes immediately after enabling it.
For Administrators
Step 1: Confirm the module is in your package
What to do: Check whether the module you need is included in your account's package. Packages control which modules are available, the seat limit and the storage limit. If the module is not included, the toggle cannot make it available.
What to verify: The module appears in the list of modules for your account.
Step 2: Enable the module
What to do: Switch on the module you need and Save.
What to verify: The module's feature appears in the navigation for a role that has permission to it.
Step 3: Set the permission scopes the module brought with it
What to do: Activating a paid module inserts its role permissions automatically. Set the scope each role should have rather than accepting the inserted defaults. For example, the Budget module brings six ownership-scoped permissions covering view, add, edit, delete, approve and its settings.
What to verify: A user in each role sees the records you intend, and only those.
Step 4: Complete the module's own settings
What to do: Several modules add their own settings area. Complete it before rolling the module out. Examples documented in CrmLeaf include Budget settings, Solar installation settings and Construction settings.
What to verify: The module's settings screen has been saved and the feature behaves as configured.
Step 5: Announce and verify
What to do: Tell the affected users where the new feature is. Because navigation is configured per edition, the feature may appear in a different group than they expect, and users can pin it to Quick Access.
What to verify: A user in the relevant role can reach the feature and complete one real task.
Add-On Modules by Area
| Area | Add-on modules |
|---|---|
| Procurement and manufacturing | Purchase, Manufacture, Goods Return |
| Project financials and delivery | Budget, Project Roadmap, Resource Utilization |
| HR and payroll | Payroll, Recruitment, Performance, Biometric, Letter, Asset |
| Support | Email Ticketing |
| Verticals | Construction, Solar Installation |
| Finance integrations | QuickBooks, Tally, E-Invoice |
| Communications and meetings | SMS and WhatsApp, Zoom, Calendly, Fireflies, CRM email integration, DocuSign |
| AI and content | AI tools, AI blog automation, QR code, Biolinks |
| Platform and developer | REST API, Public API, Webhooks, Zapier, Drive integration, Subdomain, Cyber Security, Language Pack, Affiliate, CRM insight reports |
Expected Result
The module is enabled for your account, its role permissions exist and carry deliberate scopes, its own settings are configured, and its feature appears in the navigation for the roles that need it.
Service Organisation Context
Projects, tasks, time tracking, timesheets, expenses and tickets are core, but four capabilities service organisations ask for early are paid add-on modules that must be available under your package and switched on: Budget for project budget against derived actuals, Resource Utilization for availability, capacity, workload and timeline views, Project Roadmap for delivery progress against hours, and Email Ticketing for turning a support mailbox into tickets. Confirm these are in the package before committing to a delivery head that the views will exist. The same package rules govern the Purchase, Manufacture, Construction and Solar modules that product-based and site-based businesses rely on.
Important Notes
- Menu names and their position can differ between product editions and can be customised for your account, so your sidebar may not match these paths exactly. Use Search or your Quick Access items if you cannot find a screen.
- Add-on modules are plan-gated. Confirm a module is included in your plan before you build a process around it.
- A module that is not enabled cannot be exposed by a menu layout. Menu configuration changes placement, never access.
- Seat limits and storage limits come from the package, not from the module toggles.
- Some modules depend on others in practice. Vendor, purchase order, bill and payment features need Purchase; RFQ and vendor quotes need Manufacture; budgets need Budget.
- Enabling a module changes what your whole account can reach. Plan the permission scopes at the same time.
Common Scenarios
Example: adding procurement. A Worksuite account starts buying materials. The Administrator confirms Purchase is in the package, enables it, sets the vendor and purchase order permission scopes, creates warehouses, and the procurement features appear for the buying team.
Example: a missing screen. A project manager reports that the Budget tab is not on their projects. The Budget module ships disabled, so the Administrator enables it and sets the six budget permissions. The tab then appears.
Troubleshooting
| Issue | Possible Cause | Resolution |
|---|---|---|
| A module is not in the list | The account's package does not include it | Review the package before planning the process. Contact your provider about the plan. |
| The module is enabled but users cannot see the feature | The role has no permission for it, or the permission scope is none | Set the scope in roles and permissions. |
| The feature is missing for one edition only | The feature is gated to specific product editions | Confirm the feature applies to your edition. |
| You cannot add more users after enabling a module | The account has reached the package seat limit | Review the plan or free up seats. Seat limits are set by the package. |
| Uploads fail | The account has reached the package storage limit | Review the storage limit and your storage configuration. |
Frequently Asked Questions
Why can I not see a module that I know CrmLeaf offers?
Most modules are paid add-ons. They must be included in your package and enabled for your account before they appear.
Does enabling a module give everyone access?
No. It inserts the module's role permissions. You still set the scope each role receives.
What happens to my data if a module is disabled?
Who changes my package?
Packages, subscriptions and billing are managed at platform level by your provider.
Related Articles
Our support team answers on business days. Reference PLT-07 so we can jump straight in.