About The Project QAwork Test Management System is a closed multi-project QA workspace for test execution, environment-based status tracking, reporting, planning control, checklist management, AI-assisted checklist drafting, manual checklist creation, exports, settings, and project-level administration. Each project can have its own users, planning flow, checklists, scenarios, tests, environments, references, analytics configuration, reports, and visibility settings.

Closed Access QAwork is a closed private platform. It is not a public service and does not provide open self-registration. Access is granted only to approved users who are invited into a specific project by the platform owner, a super admin, or a project administrator. Access may be refused, limited, or removed if the user is not on the approved access list.

Platform Features The platform currently includes guest tour screens, email/password login, optional Google sign-in, project selection, dashboard overview, Test Execution, QA reports and analytics, Planning Control, Checklist Builder With AI, Manual Checklist Builder, Checklist Edit, checklist/scenario/test editing and deletion, Team Access, settings, account deletion, project switching for users assigned to more than one workspace, accessibility controls, and project-level export flows such as analytics and Excel downloads where enabled.

Issue Tracking And Jira Sync QAwork includes internal bug/task tracking, issue comments, attachments, notifications, links from issues back to tests, manual Jira issue linking, and optional Jira status/metrics sync where a project admin configures Jira API access. QAwork may move synced linked Jira tickets out of open counters when their Jira status matches the configured solved statuses.

AI Usage Limits AI actions are a shared project resource. QAwork may count AI requests for features such as AI checklist creation, AI issue drafting, and Find Test with AI. Limits may be changed by project admins, super admins, or platform administration. Optional support helps fund AI infrastructure, but it does not automatically guarantee extra usage unless QAwork publishes a specific plan that says so.

Pending Tests And Tester Suggestions Testers may suggest missing tests or checklists when a bug belongs to a test that does not yet exist. Suggested tests can remain pending until a project admin or QA Lead reviews and approves them.

Account Responsibility Users are responsible for keeping their login details private and for using only the projects they were approved to access. Sharing credentials, trying to access another project without permission, or using the platform outside the approved QA workflow is not allowed.

Admin Responsibility Project admins are responsible for managing team access, validating checklists, reviewing AI-generated drafts, checking uploaded content, confirming report data, and keeping project configuration accurate. Admin actions can affect what testers see and what data is included in reports.

Project Owner Responsibility Each project owner and project administrator is responsible for the project workspace, the users they allow into it, the checklists, scenarios, test cases, bug records, uploaded files, Jira settings, exported reports, and any business decisions made from that data. QAwork administration provides and maintains the platform, but it is not responsible for how a project owner, admin, QA Lead, tester, or invited user uses the workspace or interprets its results.

Editing, Deleting, And Changing Project Data Project users with the required permissions may create, edit, rename, move, archive, delete, or otherwise change project data, including checklists, scenarios, test cases, test results, issues, comments, environments, settings, team access, and uploaded references. These actions may affect reports, analytics, visibility, and future test execution. The project owner and project admins are responsible for reviewing who has permission to make these changes and for the consequences of those changes inside their project.

Test Execution And Reports Test statuses, environment results, pass rates, regressions, risks, trends, and other analytics are operational QA summaries. They help teams understand project quality, but they are not a guarantee that a product is defect-free or ready for release.

Links, References, And External Content Projects may include related Jira links, documentation links, Google Sheets links, uploaded chart images, and other external references. QAwork provides a structured place to keep these references connected to tests, but the platform owner does not guarantee the availability, correctness, or security of third-party resources.

AI Assistance AI features inside QAwork are designed to help draft checklist structure, scenario names, test titles, descriptions, expected results, and negative checks. AI output is assistive only. Project admins are responsible for reviewing, editing, and approving anything before it is published into the real checklist structure.

Uploads And Exports Users and admins should upload only files and references they are allowed to use inside the project. Exported reports, Excel files, analytics, and copied project data should be handled as private project information and shared only with approved people.

Project Separation Each user should only see the projects they were assigned to. Data, navigation, and permissions are intended to stay separated by project. If you believe you can access the wrong project or the wrong data, contact the platform owner immediately.

Account And Project Deletion Users may delete their own account from settings. If the deleting user is the only active admin of one or more projects, QAwork may warn that those projects will also be removed because they would no longer have an administrator. Testers may still delete their own account even when they belong to active projects.

Use At Your Own Discretion The owner and provider of QAwork do not accept responsibility for how a project workspace is used by its project owner, admins, QA Leads, testers, or invited users; for decisions made based on platform output; or for uploaded content, edited data, deleted data, exported files, external links, and third-party integrations used through the system.

Current Status And Pricing The platform is currently closed and available only by approval. At the present stage, its use is free of charge. In the future, when QAwork administration decides the timing is right, project subscriptions may become paid. This closed-access status and pricing model may change in the future without prior notice.

Subscription And AI Actions QAwork may introduce paid subscription plans in the future. Future plans may include AI actions, project limits, storage, integrations, support levels, or other workspace capabilities. Administration may change the free stage, enable paid subscription plans, or adjust AI usage limits at any time.

Support Project QAwork may display optional project-support links such as Buy Me A Coffee. Support is voluntary and helps with hosting, maintenance, development, and AI infrastructure costs during launch. Support is not a hidden payment requirement, does not replace these Terms Of Use, and does not guarantee permanent free access, fixed limits, extra AI usage, or fixed future pricing unless QAwork publishes a specific plan that says so.

Contact For questions about the platform, access, or usage, email [email protected].