Understand QCST Component Permissions and Administrator ACL
This article explains core.manage/core.admin plus qcst.manage_settings, qcst.manage_license, portal/ticket/agent/department/response permissions and how they affect backend access.
Where this fits in QC Support Ticket
QCST separates customer access, frontend support work, and Joomla administrator configuration. A QCST Frontend Agent can work tickets in the Agent Queue without being granted Joomla backend administration, while administrator actions remain governed by Joomla ACL and QCST-specific permissions.
Primary location: Joomla Administrator → System → Global Configuration → QC Support Ticket permissions, plus QCST role/scope controls.
Current permission map
| Permission | Practical meaning |
|---|---|
| core.manage / core.admin | Administrator component access / Joomla administrative authority. |
| qcst.manage_settings | Manage QCST configuration and organization setup. |
| qcst.manage_license | Manage entitlement/legacy-key controls. |
| qcst.use_portal | Use the frontend customer portal. |
| qcst.submit_ticket | Submit a ticket where other checks permit it. |
| qcst.view_own_tickets | View the current customer's own tickets. |
| qcst.agent_access | Enter the frontend Agent Queue when the user also has an active QCST Agent record. |
| qcst.manage_tickets | Perform ticket-management actions subject to department scope. |
| qcst.manage_departments | Manage department-scoped organization data. |
| qcst.manage_responses | Manage canned responses where entitled. |
Two checks often apply
A Joomla/QCST permission can allow use of a feature, while ticket ownership or Agent Department scope still limits the specific record. Granting qcst.agent_access does not make every ticket visible to that Agent.
Important behavior and limits
- The current administrator interface has nine tabs: About, Support, Status, Settings, Tickets, Canned Responses, Email Templates, Frontend Design, Frontend Text.
Key fields and behavior
| Item | Current behavior |
|---|---|
| core.manage / core.admin | Backend component administration |
| qcst.manage_settings | QCST settings/configuration |
| qcst.manage_license | Entitlement/preview actions |
| qcst.use_portal | Use customer portal |
| qcst.submit_ticket | Create tickets |
| qcst.view_own_tickets | View own tickets |
| qcst.agent_access | Enter Agent Queue |
| qcst.manage_tickets | Ticket management actions |
| qcst.manage_departments | Organization/Department management |
| qcst.manage_responses | Canned response management |
Design ACL around responsibilities
- Give day-to-day Frontend Agents the frontend Agent role/scope they need; do not grant Joomla Administrator access merely so they can answer tickets.
- Give support managers only the QCST administrator actions required for their job, such as ticket or Department management.
- Reserve
qcst.manage_licenseand broader Joomlacore.admincapabilities for administrators who genuinely manage entitlement or global permissions. - After changing ACL, sign in as a normal member of the affected Joomla group and test both an allowed and denied action.
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.