Joomla Integration Plugins Installed with QC Support Ticket
This article explains the package roles of Task, Privacy, User, Content, Finder, Action Log, and Webservices integrations without presenting dormant API-token/webhook management as a customer UI.
Where this fits in QC Support Ticket
QCST installs as a Joomla package with companion integration plugins. Each plugin has a Joomla integration role, but the presence of a plugin or internal service does not imply that QCST exposes a corresponding customer configuration screen.
Primary location: QC Support Ticket frontend and administrator interfaces, depending on the permission or failure being tested.
Package integrations
| Plugin/integration | Role |
|---|---|
| Task | Runs the five current QCST Scheduled Task routines. |
| Privacy | Participates in Joomla privacy/export/removal integration where applicable. |
| User | Responds to Joomla user lifecycle integration needed by QCST ownership/Agent data. |
| Content | Provides QCST content integration hooks used by the package. |
| Finder | Integrates relevant QCST data with Joomla Smart Search where supported. |
| Action Log | Adds relevant QCST administrator/user actions to Joomla action logging. |
| Webservices | Provides the packaged integration surface; its existence does not mean there is a current API-token management UI. |
Key fields and behavior
| Item | Current behavior |
|---|---|
| Task | Joomla Scheduled Tasks routines |
| Privacy | Privacy integration |
| User | User lifecycle integration |
| Content | Content integration hook |
| Finder | Smart Search integration hook |
| Action Log | Joomla action-log integration |
| Webservices | Webservices integration package; its presence does not create a current customer API-token/webhook management screen |
Current-version note
This documentation is based on QC Support Ticket 1.0.42, the package currently deployed on the QuantaCade production site. The behavior described for Joomla Integration Plugins Installed with QC Support Ticket should be checked against the current screen labels before applying instructions to an older QCST release.
Do not manage package plugins as optional features casually
The package is designed to install its companion integrations together. Disabling/removing one because its role is not obvious can break privacy, task, user-lifecycle, search, logging or other Joomla integration behavior. When troubleshooting, compare the installed package/plugins with the current package manifest before deciding an integration is unnecessary.
Community Discussion
For practical QC Support Ticket workflows and discussion with other Joomla site owners, visit the QC Support Ticket Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.