Module Planning and Activation
Choose CMS modules, understand dependencies and entitlement, and verify activation after installation.
The core CMS supplies shared users, access controls, settings, files, communication, and other platform services. Modules add business workflows on top of that core.
Choose by business need
The public catalog includes capabilities such as auctions, appraisals, sales, collections, invoicing, projects, support, collaboration, time clock, marketing, blog, and podcasting. Use the current product configurator to confirm what is purchasable and included in your edition.
Do not treat a marketing page as proof that a module is included in your license. The purchased service's module configuration determines its paid entitlements.
Check dependencies and infrastructure
A module can require another module or a shared provider. Review its dependency information before purchasing or disabling related capabilities. For example, auction workflows use invoicing functionality.
For planning, ask:
| Requirement | What to prepare |
|---|---|
| Email or SMS | A configured communication provider and verified sender |
| Payment collection | A configured CMS gateway and tested callbacks |
| Live collaboration or bidding | Working WebSocket ingress and the appropriate Redis/process topology |
| Images and documents | Persistent local uploads or a supported external provider |
| Streaming or conferencing | The provider and network resources required by that module |
The detailed settings and business workflows belong to the module documentation inside your CMS.
Understand three states
Shipped means the module's files are present. Entitled means your license includes the paid capability. Installed and enabled means the CMS has applied the module's setup and activated it.
These are different checks. A directory in the release is not an entitlement, and an entitled module can still have a configuration or migration problem.
Activate and verify
After installing the CMS, open Admin → Modules. Review the available modules, installation and enabled state, dependency information, and required configuration. Use the supported install, enable, and configuration controls as applicable.
Module migrations are managed by the platform during startup and supported module lifecycle operations. If a module is unavailable, check license entitlements, required dependencies, and startup migration logs before running repeated install attempts.
License changes arrive on a subsequent successful validation; a fresh local cache can delay the update. Contact support if the portal entitlement is correct but the CMS still does not recognize it.
Disable with a plan
Before disabling a module, identify other modules and staff workflows that depend on it. Take a backup and review its data-retention behavior. Disabling, uninstalling, and wiping module data are different operations; do not use destructive data actions simply to troubleshoot visibility.
Keep development utilities such as Example and Debug Tools out of normal staff workflows unless there is a deliberate operational reason to expose them.
Find the usage manual
Open Documentation in the CMS administration area at /admin/docs. The available documentation follows the installed module set. Use it for the procedures your staff perform after activation.