AWP Support Desk ships four dedicated WordPress roles, so support staff do not need to be administrators and customers do not need any wp-admin access at all. Assigning one takes a minute under Users → Profile, and the plugin keeps the roles in sync after updates. The roles are created on activation and survive plugin deletion unless you opt in to full data removal. This guide explains what each role can do, how the capability model works and how to adjust the matrix for your team. If you are still installing the plugin, start with the installation guide.
The four roles #
| Role | Label in WordPress | What it can do |
|---|---|---|
awp_admin |
Support administrator | Everything: settings, roles, reports and every ticket. |
awp_manager |
Support manager | Everything an agent can do, plus reports, categories, agent management and ticket deletion. |
awp_agent |
Support agent | Answers tickets, replies, assigns, changes status, priority and category, uploads attachments and manages canned replies. |
awp_customer |
Support customer | Opens tickets from the portal and follows only their own conversations. |
The labels above are what WordPress shows on user screens; the slugs are what you will see in code, in WP-CLI and in the capability matrix. A person can also hold more than one role; WordPress merges the capabilities of all of them.
How capabilities work #
The roles rest on 16 granular capabilities, all prefixed with awp_, such as awp_reply_tickets, awp_assign_tickets, awp_view_reports or awp_manage_settings. Four of them are per-ticket checks resolved through WordPress map_meta_cap, so “view tickets” really means “view this ticket if you are allowed to”.
Because those checks run per ticket, permissions hold even against manipulated links: a customer who can read their own ticket still cannot open another customer’s ticket by editing the URL. The WordPress administrator role holds every AWP capability automatically, so you never lose access by delegating.
The model also draws lines nobody can cross from the screens: customers cannot reply to other people’s tickets, agents cannot delete tickets or view reports, and configuration stays with roles that hold awp_manage_settings.
Customers never see wp-admin. An awp_customer account can log in to WordPress, but its workspace is the customer portal: the ticket list, the conversation threads and the attachment downloads. Nothing else is reachable.
Common team setups #
| Setup | Who to add |
|---|---|
| You handle support alone | Keep it on your WordPress administrator account; it already holds every capability. |
| Owner plus a few agents | awp_manager for the owner, awp_agent for the team. |
| Growing desk | awp_manager for supervisors, awp_agent for agents, awp_customer for customer accounts. |
| Support plus freelancers | awp_agent for external collaborators — no reports, no settings, no ticket deletion. |
Whichever setup you choose, give every staff member a personal account. Shared logins blur who replied what, and the audit trail works best when actions belong to one person each.
Adjust capabilities #
- Open Support Desk → Roles.
- The matrix lists the support roles and the capabilities each one holds.
- Toggle the capabilities a role should keep and save.
- Check the result with a test account before applying it to the whole team.
- If a change goes wrong, use the reset button to restore the default matrix.
The matrix is role-scoped on purpose: an agent cannot be promoted into manager-only capabilities from this screen, and a customer can never receive staff capabilities. The screen itself is protected by its own capability, so only roles you explicitly grant it can change the matrix. Updates respect your decisions too — a plugin update adds new default capabilities but never restores one you revoked. Changes apply immediately; there is no cache to clear and no user to re-save.
Customers never see wp-admin #
Creating a customer account is ordinary WordPress user management: Users → Add New, choose the Support customer role, and send the person the portal link. Their login takes them to the portal, where they see their own tickets and nothing else.
This keeps support self-service without opening the dashboard. It is also why notification emails link back to the portal rather than to wp-admin — the customer never needs a backend screen to follow a conversation.
Next steps #
See the roles in action: agents work day to day in the agent inbox, and customers in the customer portal. The product page describes the full permission model and what the Pro add-on adds, such as teams with round-robin assignment.