PQM Training Help
PQM Training / Help and PQM Training
Help and PQM Training
Find documentation, role guides, FAQ, support path and practical onboarding instructions.
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
Help and Training is the safe guidance area for users who do not know what to click next. It should collect documentation, training lessons, support links, setup instructions and quick explanations of the most common screens.
For a beginner, this page should reduce fear. If the user is lost, they should open Help and find a clear path: setup, create task, manage production, communicate, report and troubleshoot.
Where to click
What Help should contain
| Help area | Purpose | Beginner expectation |
|---|---|---|
| Quick start | Shortest route from install to first task. | “Tell me what to click first.” |
| Training pages | Longer lessons with screenshots and examples. | “Explain the screen like I am new.” |
| Role guides | Separate guidance for admin, manager, worker and client. | “Show me only what matters for my role.” |
| FAQ | Common questions and problems. | “Why is my task/report/email not visible?” |
| Support / contact | Where to get help if documentation is not enough. | “How do I contact support and what information should I send?” |
| Version / changelog | What changed in recent versions. | “Did this feature move or change?” |
What to prepare before asking support
Mini FAQ for beginners
| Question | Answer |
|---|---|
| Where do I start after installation? | Run Setup Wizard, then create a test task, then check dashboard and task list. |
| Why do reports look empty? | Usually there is no data in the selected date range or tasks do not have the status/date required by the report. |
| Why does a worker not see tasks? | The user may not be assigned to the correct department or role/capability. |
| Why did the customer not receive an email? | Check recipient address, email queue status and WordPress/SMTP mail configuration. |
| Can I use PQM without WooCommerce? | Core task workflow can be independent depending on build; WooCommerce integration is useful when online orders should become tasks. |
Good practice
- Write help content for the newest employee, not for the developer.
- Use consistent screen names. If the menu says “Tasks”, do not call it “Jobs” in help text unless you explain the difference.
- Keep help linked from every complex area.
- Update Help after every major UI change, not only after code changes.
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.
Who should use this screen?
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. |


