PQM Training / Core Configuration

System Foundation

Core Configuration

Define the production logic: departments, statuses, roles, permissions, defaults, reports and workflow rules.

Production OSWordPress CoreRole-based workflowTraining Center

Training pages

Training Home Production Dashboard Core Configuration Tasks and Add Task Departments and Workflow Calendar and Standard Gantt Email Queue and Communication Reports and KPI Modules / Marketplace Setup Wizard License and Demo Mode Help and Training Admin Panel Client Panel Employee Worker Portal Shop Manager / Supervisor Implementation Checklist

Purpose in plain language

Core Configuration is where the basic production logic is defined. A task list can only be useful when PQM knows what statuses exist, what departments exist, which roles are allowed to perform actions, and how the company wants to work.

For a beginner, this screen is like preparing the production map before the team starts driving. If the map is wrong, reports, dashboards, employee portals and customer communication will also be confusing.

Where to click

Open PQM from the WordPress admin menu.

Choose Settings, Core, Configuration or Admin Panel, depending on the build.

Do not change everything at once. Start with departments, statuses, roles and email basics.

After every important change, create or open a test task and confirm the change is visible in real workflow screens.

Safe configuration order

1. DepartmentsReal stages

2. StatusesProgress states

3. RolesAccess control

4. EmailsNotifications

Important

Do not start with modules, dashboards or reports. They depend on the core structure. A beautiful report built on wrong statuses will still give wrong information.

Settings map for non-technical users

Setting group	Beginner explanation	Typical decision
Departments	Real teams or production stages that perform work.	Design, print, finishing, packaging, shipping.
Statuses	Task progress labels used in lists, dashboards, reports and emails.	New, accepted, in progress, waiting, completed, cancelled, complaint.
Task defaults	Default values used when a new task is created.	Default status is New; default priority is Normal; default deadline may be empty or calculated.
Permissions / capabilities	Rules that decide what each role can see and change.	Workers update assigned stages; managers create tasks; admins change settings.
Email settings	Which notifications are allowed and which templates are used.	Send customer email on task creation and completion in the Free/basic workflow.
WooCommerce integration	Connects online orders with production tasks if WooCommerce is used.	Create tasks from orders and use WooCommerce currency/totals where needed.
Reports configuration	Decides how production data is interpreted.	Cancelled tasks should not distort normal production reports.

First setup step by step

Write the real production process on paper before changing settings. Example: order received → design → print → finishing → quality check → shipping → completed.

Create only the departments that the company actually uses. Avoid fantasy departments that nobody is responsible for.

Create or confirm statuses. Keep them simple. Too many statuses confuse workers and destroy report quality.

Create one manager user, one worker user and one test customer/client user. Never test every role only as administrator.

Create one manual task and move it through the workflow. Check dashboard, calendar, employee portal and reports after each change.

Only after the basic workflow works, enable extra modules or advanced options.

Status rules that keep reports clean

Status type	Meaning	Recommended reporting behavior
New / accepted	The task exists but production may not have started.	Visible in open task counts and new work lists.
In progress	A department or employee is actively working.	Visible in active production and workload views.
Waiting / paused	Work is blocked by missing file, customer decision, material or approval.	Should not be forgotten; may need separate attention.
Completed / _end	Production is finished and the task should be archived/locked depending on configuration.	Used for done counts, completion trends and on-time calculations.
Cancelled / _canceled	The task is not part of normal production anymore.	Usually hidden by default and excluded from normal production reports.
Complaint / _complaint	Task requires complaint handling or correction process.	Should be visible for service quality control, not mixed with normal completed jobs.

Good practice

Keep core configuration boring and predictable. Production systems work best when workers do not need to guess.
Name departments using real company language, not developer language.
Test every permission change with a non-admin account.
Before deleting or renaming a status, check whether old tasks and reports depend on it.
Document your final workflow in the training pages so future employees understand it.

Screenshot reference

How to use screenshots

Click any screenshot to open it in a new tab. This is useful for zooming in while following the step-by-step instructions.

Core Configuration

Core configuration screen reference. Use it when explaining base settings, roles, statuses and production defaults.

Who should use this screen?

AdministratorConfigures PQM, licenses, modules, health checks, capabilities and technical maintenance. This role should be limited to trusted users.

Manager / Shop ManagerControls daily production, creates tasks, checks reports, follows deadlines and supervises employee work without changing technical settings.

Production EmployeeWorks mainly in the frontend Employee Portal and updates assigned production stages without using the WordPress admin area.

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.

Readiness checklist

A beginner can explain what this screen is for after reading the first two sections.

The correct role can open the screen and restricted roles cannot see unsafe actions.

There is at least one realistic test task visible in the screen.

Buttons and links go to the expected place.

The empty state explains what to do next instead of looking broken.

The page remains readable on tablet and mobile.

Related training pages

Training HomeTraining overview and recommended learning path.Production DashboardDaily command center, active tasks, metrics and quick actions.Tasks and Add TaskHow to create, read and update production tasks step by step.Departments and WorkflowHow production stages and responsibilities are modeled.Calendar and Standard GanttDate planning, deadlines and visual timeline overview.Email Queue and CommunicationCustomer messages, email queue and communication templates.Reports and KPIKPI, margins, bottlenecks, exports and production analysis.Modules / MarketplaceOptional modules, activation state and upgrade path.

PQM Training Core