PQM Training Client Panel
PQM Training / Client Panel
Client Panel
Customer-facing area for own tasks, status updates, messages, files and production communication.
Training HomeProduction DashboardCore ConfigurationTasks and Add TaskDepartments and WorkflowCalendar and Standard GanttEmail Queue and CommunicationReports and KPIModules / MarketplaceSetup WizardLicense and Demo ModeHelp and TrainingAdmin PanelClient PanelEmployee Worker PortalShop Manager / SupervisorImplementation Checklist
Purpose in plain language
Client Panel is the customer-facing area. It lets a customer see their own task/order information, read production updates, send messages or download relevant files without entering the WordPress admin dashboard.
For a beginner, this panel reduces phone calls and scattered emails. Customers should not need to ask “what is happening with my order?” if the panel explains the current state clearly.
Where to click / how customer opens it
Client Panel areas
| Area | What customer sees | What should be hidden |
|---|---|---|
| Task/order list | Only tasks/orders belonging to this customer. | Other customers’ data, internal task list, admin controls. |
| Status | Simple production state such as received, in production, ready, completed. | Internal technical statuses that confuse customer. |
| Messages | Customer-safe communication connected to the task. | Internal notes, cost calculations, employee comments. |
| Files | Proofs, approved files, documents intended for customer. | Internal production files or files from other clients. |
| Dates | Promised date, expected completion, pickup/delivery info if available. | Internal planning data not suitable for customer promises. |
Customer workflow step by step
Security and privacy rules
The customer panel must not show other customers, internal cost calculations, private employee notes, license/admin data, module diagnostics or raw technical errors.
| Data type | Customer can see? | Reason |
|---|---|---|
| Own task title/status | Yes | Customer needs basic progress information. |
| Own customer-safe messages | Yes | Communication should be transparent. |
| Other customers’ tasks | No | Privacy and commercial confidentiality. |
| Internal notes | No, unless intentionally published | Production comments may be inappropriate or confusing. |
| Costs/margins | No | Business internal data. |
| Admin settings/license | No | Technical/security data. |
Good practice
- Use customer-friendly status labels. Customers do not need every internal department detail.
- Always test the panel with a real customer-role account, not administrator.
- Keep messages short and clear. The panel is for service communication, not developer diagnostics.
- When file download is enabled, confirm ownership checks before publishing.
Screenshot reference
Click any screenshot to open it in a new tab. This is useful for zooming in while following the step-by-step instructions.
Troubleshooting for beginners
| Symptom | Simple explanation | What to check first |
|---|---|---|
| The page looks empty | The system may have no demo data yet, or the current user may not have access to the required role/capability. | Create one test task, assign a department, then refresh the screen. Also check the user role. |
| A button opens a login page or My Account | The visitor is not logged in or the page is using a frontend-safe route that requires authentication. | Log in with a test user that has the expected role. Check whether the shortcode/page is visible only to logged-in users. |
| Data exists but does not appear in a report/chart | Filters, date range, status rules or completion dates may exclude the task. | Clear filters, expand the date range and verify that the task has the status/date required by the report. |
| Something changed but the screen still shows old data | Browser cache, WordPress cache or AJAX response cache may show old information. | Refresh the page, clear cache for this page and test in an incognito window before debugging code. |
| The layout is broken on a small screen | Wide tables and timelines need horizontal space; this is normal if the content remains readable. | Use the mobile breakpoint, keep cards in one column and allow horizontal scroll only inside tables/timelines. |


