QStack Help¶
QStack is your electronic Quality Management System (eQMS). It replaces paper binders, shared-drive folders, and Excel logs with one place to author and approve controlled documents, capture evidence that work was done, track training, run deviations and CAPA, manage vendors and audits, control change, and handle complaints — all with electronic signatures and a tamper-evident audit trail behind every action.
QStack is deliberately opinionated: there is one way to run each process, so the system itself behaves like your SOP. You won't find a workflow designer or custom fields to configure — just the modules below, ready to use.
The modules¶
| Module | What it's for |
|---|---|
| Quality Documents | Author, review, approve, and publish SOPs, work instructions, policies, forms, and other controlled documents |
| Quality Records | Capture evidence that controlled work was performed — filled-in forms and uploaded external documents like vendor certificates |
| Training | Know who needs to be trained on what, and prove it — role-based matrix plus one-off assignments |
| Deviations & CAPA | Log unexpected events, investigate root cause, act on it, and check the action worked |
| Vendors & Audits | Maintain your approved-supplier list and run internal and supplier audits |
| Change Control | Assess, approve, implement, and verify changes to anything that affects product quality |
| Complaints | Capture, triage, investigate, and respond to product-quality complaints |
| Notifications & Reporting | Your task inbox, email reminders, and the quality metrics dashboard |
| People | Persons, job functions, workflow roles, and the manager chain that drives training and escalation |
| Electronic Signatures | How signing meanings, re-authentication, and the signing log work everywhere in QStack |
| Onboarding | Importing your existing documents, people, and vendors when you first set up QStack |
Finding your way around¶
Every module page is organized around the tasks you actually do — logging a deviation, authoring an SOP, adding a vendor — with numbered steps where there's a procedure to follow. Look for:
Tip
Admonitions like this one call out things worth knowing before you start a task — a precondition, a blocking rule, or a shortcut.
Cross-references between pages are linked inline, so if a task in one module depends on another (for example, a CAPA action that opens a training assignment), you can follow the link straight there.
Getting help¶
Start with your task inbox — it's the default page you land on after login, and it lists everything QStack thinks you need to act on today. If a task is blocked, the page for that module explains the precondition that's blocking it.
If this help site doesn't answer your question, contact your Quality role holder or your Org Admin — they can see the same pages you can, plus the tenant-level configuration decisions described on each module's "decisions for the customer" areas.