Upgrade
Quality

Quality centre

Review QA, accessibility, performance, security, browser, mobile, routes, workflows, permissions, evidence, issues, and release gates in one place.

Public statusSeller qualityAdmin quality
quality domains18

Routes, workflows, evidence, issues, release gates, and readiness

event hooks22

Audit, evidence, coverage, checks, issues, gates, and readiness events

governance controls16

Evidence validity, route, security, mobile, API, and launch policies

Seller quality workspace

Seller-scoped quality checks show route, workflow, mobile, accessibility, performance, and issue references without blocking access to core tools.

manual QA required
/dashboard/quality/readiness

Readiness

Seller-scoped quality readiness

/dashboard/quality/workflows

Workflows

Seller workflow QA references

/dashboard/quality/issues

Issues

Seller-visible blockers and remediation references

/dashboard/quality/accessibility

Accessibility

Accessibility checks and manual QA reminders

/dashboard/quality/mobile

Mobile

Mobile usability and breakpoint readiness

/dashboard/quality/performance

Performance

Performance budget and measurement references

Quality safety rules

Quality review records evidence and blockers. It does not replace final launch approval or expose private data.

public-safe

Automated tests are not human QA approval.

Accessibility checks are not accessibility certification.

Security readiness is not a penetration test.

Local performance budgets are not production Core Web Vitals proof.

Route render checks are not payment, delivery, publishing, sending, or workflow success.

Checkout, delivery, publishing, sending, payout, and billing workflows require their own live QA evidence.

Emails, social posts, paid campaigns, public content, consent controls, and public claims require human approval.

Seller-facing and public views keep sensitive credentials, private file keys, payment details, buyer private data, and support notes out of display payloads.