Overview
Activation and module utilities control whether QBM is registered, which product key is in use, and which licensed modules or additional functionality are available.
Important: These commands affect licensing and available features. Use them with the product key, client ID, and module information supplied by QBM support or the authorized implementation team.
Where To Find It
Primary Paths: Help > Register/Activate, Help > Change Key, Help > More Functionalities
Related Paths: Help > Maintenance > Add Module, Help > Maintenance > Activate Modules, Help > Maintenance > Update Product
Some commands appear only when the current edition, activation state, company connection, or user permissions allow them.
Utility Commands
| Command | What It Does | When To Use It |
|---|---|---|
| Register/Activate | Starts the activation process so QBM can validate the product key and activation information. | Use it after installation, renewal, or support instruction when QBM is not yet activated. |
| Change Key | Lets an authorized user replace the current product key and refresh QBM after the key is accepted. | Use it when support provides a replacement key, edition change, renewal key, or corrected license details. |
| More Functionalities | Opens the screen used to review or request additional QBM capabilities. | Use it when the business wants to see which extra features or editions may be available. |
| Add Module | Adds a licensed module to the connected company when the required module information is available. | Use it after QBM support or the implementation team confirms the company is eligible for the module. |
| Activate Modules | Activates available modules after the license or module setup has been added. | Use it when installed modules need to be turned on for the current company. |
| Update Product | Opens the product update utility when it is available in the current environment. | Use it only as part of a controlled update process, normally after backing up the company data. |
| Check for Updates | Checks whether application updates are available for a supported, activated installation. | Use it when planning an update or when support asks the user to verify update availability. |
Recommended Workflow
- Confirm the company, user permissions, product key, and client ID before changing activation or module settings.
- Back up the company data before update or module work that may affect the environment.
- Use Register/Activate or Change Key only with details supplied by the authorized QBM channel.
- Add or activate modules only after the business confirms the module should be enabled for this company.
- After activation or module changes, sign back in and verify that the expected menus and screens are visible.
Best Practice
- Keep product keys and client IDs private and share them only with authorized support staff.
- Do not change the key during active transaction posting or while other users are working.
- Record the reason for module activation so future support can understand why a feature is enabled.
- Use Check for Updates as a planning step, not as a substitute for a tested update process.
- If a module or key does not activate, stop and verify the supplied details before trying unrelated changes.
Troubleshooting
| Issue | What To Check |
|---|---|
| Register/Activate is not visible. | The installation may already be activated, or the menu may be hidden for the current edition or user state. |
| Change Key is not visible. | Check whether the current activation state allows key changes and whether the user has permission. |
| Add Module is blocked. | Confirm a company is connected and that support supplied valid module details for this company. |
| A new module is activated but menus do not appear. | Sign out and back in, then check edition, permissions, and any company option that controls the feature. |
| Update check is not allowed. | Confirm the installation is a full activated version and that the computer can reach the required update service. |