This guide covers implementation, configuration, daily use and troubleshooting for Small Business Management – CRM Enterprise.
Small Business Management – CRM Enterprise Implementation Guide
Product: Small Business CRM Enterprise / Small Business Management – CRM Enterprise
Version covered: 1.0.11
This guide covers Enterprise installation, Pro dependency alignment, workspaces/branches, audit logs, API/webhook foundations and scheduled report controls.
Purpose and dependency model
CRM Enterprise is the governance and scale add-on for CRM. It requires CRM Free/Core and CRM Pro. It should be used only where teams, branches, audit controls, API/webhooks or scheduled reporting are needed.
| Area | Detail |
|---|---|
| Requires | CRM Free/Core and CRM Pro active with valid paid entitlement. |
| Adds | Workspaces/branches, enterprise roles, audit logs, API keys, webhooks and scheduled reports. |
| Primary users | Enterprise Admins, regional managers, branch managers and system administrators. |
| Important limitation | The current package provides the enterprise foundation. Confirm branch-level data isolation before promising strict multi-branch separation. |
Installation order
- Install CRM Free/Core.
- Install CRM Pro and activate its licence.
- Install CRM Enterprise.
- Activate the Enterprise licence.
- Create a test workspace/branch.
- Create test users for Branch Manager, Regional Manager and Enterprise Admin.
- Confirm each role sees only the expected Enterprise menu items.
Enterprise roles
| Role | Responsibility |
|---|---|
| CRM Branch Manager | Manages branch-level sales activity when workspace scoping is implemented. |
| CRM Regional Manager | Reviews multiple branch/team areas and scheduled reports. |
| CRM Enterprise Admin | Manages enterprise settings, API/webhooks, audit logs and enterprise roles. |
| WordPress Administrator | Retains full technical control over plugin install, updates and site-level settings. |
Audit logs, API keys and webhooks
- Use audit logs to review sensitive actions and configuration changes.
- Create API keys only for trusted systems.
- Record who owns each API key and why it exists.
- Disable unused keys immediately.
- Test webhooks with a non-production endpoint before using live data.
Scheduled reporting
Scheduled reports should support management review rather than replace operational dashboards. Define recipients, frequency, report scope and data sensitivity before enabling automated delivery.
Go-live checklist
- Take a full file and database backup before installing on a production site.
- Install on a staging site first when replacing an older build or changing roles.
- Confirm the required parent plugin is active before activating a Pro or Enterprise add-on.
- Use a non-admin test user to confirm menu access and permissions.
- Create one test record, run through the full workflow, and only then import or enable real customer data.
Also verify that enterprise features do not expose data to users who should only see branch/team-level information.