Help Center

QAForgeHub is currently invite-only: ordinary self-registration is unavailable. You need a valid invitation link to create an account — the registration page explains this and lets you log in instead if you already have one.

The most common way to get an account during invite-only access is through an organization invitation: someone who's already an Owner or Administrator of an organization invites your email address, you open the link, and you set your own password right there. Submitting the form creates your account and adds you to that organization in one step — see Managing Members & Invitations, below, for the full flow.

All work in QAForgeHub — projects, issues, sprints — belongs to an organization. An organization is a separate company workspace with its own projects, members, permissions, and billing. You can create your own organization, or join an existing one through an invitation.

If you belong to more than one organization, use the organization switcher in the top navigation bar to change which one you're currently working in. Being a member of another organization never affects your own.

Most companies only need one organization. Use projects to separate products, applications, or workstreams inside it. For example, a company called DleetSoft would have one organization with projects for QAForgeHub, QAForge Desktop, and MindMesh — not a separate organization per team or per department.

Create a separate organization only when you genuinely need a separate tenant and billing boundary — a different company, an independent client workspace, or a division with its own subscription. Each organization has its own members, permissions, data isolation, and plan.

• Your first organization is free — up to 3 projects and 5 members.
• Each additional organization you create needs its own Pro subscription before it can be used.
• A person can belong to as many organizations as they like. Pro is billed per organization, not per member — being invited into an organization never charges you personally.

• Dashboard — an overview of your active organization's recent activity.
• Projects — the list of projects in your active organization, and where you create new ones.
• My Issues — every issue assigned to you across your projects.
• Search — the search field in the header finds issues, projects, and other work by name.

Once you're inside a project, a project-level navigation bar gives you access to that project's Backlog, Board, Sprints, Planning Poker, Roadmap, and Reports.

Every member of an organization holds exactly one role, which determines what they can see and do. An Owner or Administrator assigns a role when they invite someone, and can change it later from the Members page.

• Owner — Manage organization settings, members, invitations, billing, projects, issues, Sprints, Planning Poker, and reports.
• Administrator — Manage organization settings, members, invitations, billing, projects, issues, Sprints, Planning Poker, and reports.
• Project Manager — Manage projects, issues, Sprints, Planning Poker, and reports.
• Developer — Create and work with issues and Planning Poker.
• Tester — Create and work with issues and Planning Poker.
• Viewer — Read-oriented access with limited interaction.

The Owner is the person with ultimate control of the organization. An Administrator is a trusted teammate who can handle normal day-to-day organization operations — inviting people, managing members, and handling billing — but cannot take ownership away from the Owner.

• An Administrator can see the Owner in the Members list, but cannot change the Owner's role, remove the Owner, or promote themselves to Owner.
• Only the Owner can transfer ownership to someone else. Ownership transfer is a deliberate, explicit action — it never happens as a side effect of an ordinary role change.
• Every organization should always have exactly one Owner. If the Owner leaves the team, transfer ownership to someone else first.

Three administrative surfaces are restricted to the Owner and Administrator roles only. Project Manager, Developer, Tester, and Viewer never see these, whether from the navigation or by visiting the page directly:

• Members — inviting people, changing roles, and removing members.
• Organization Settings — organization-wide configuration.
• Billing — the organization's plan, subscription, and usage.

Project Manager, Developer, Tester, and Viewer instead work within projects: creating and managing issues, Sprints, and Planning Poker sessions according to their role, without any organization-administration access.

Only an Owner or Administrator can open the Members page, invite new people, change a member's role, or remove a member. Other roles won't see Members in the navigation, and opening its URL directly doesn't work either.

From the Members page, an Owner or Administrator enters the person's email address, chooses a role for them, and sends the invitation. QAForgeHub emails an invitation link to that address.

1. The invited person opens the link and sees which organization they've been invited to join and what role they'll have.
2. Their invited email address is shown but can't be changed — the invitation only works for that address.
3. If they don't already have a QAForgeHub account, they choose their own name and password right there — no administrator ever sets or sees a temporary password for them.
4. Submitting the form creates their account and adds them to the organization immediately, with the role they were invited as.

Invitation links are only valid for a limited time and can only be used once. If a link has expired, or already used, opening it shows a clear "invitation not valid" message rather than an error page.

An Owner or Administrator can resend an invitation from the Members page. Resending creates a fresh link and immediately invalidates the previous one — if someone reports that an old link doesn't work anymore, check whether the invitation was resent.

An Owner or Administrator can change any member's role from the Members page — the change takes effect immediately, including removing that person's access to anything their new role no longer permits. Neither role can change the Owner's role or remove the Owner; only ownership transfer can do that.

From your organization's page, choose to create a project and give it a name and a short project key (used as the prefix on every issue's identifier, e.g. ABC-1). Once created, the project appears in your organization's project list.

• Backlog — unscheduled issues, ready to be pulled into a Sprint.
• Board — a Kanban-style board of issue status, with a List view available too.
• Sprints — creating and running Sprints.
• Planning Poker — estimation sessions tied to individual issues.
• Roadmap — milestones grouped by status.
• Reports — project updates published by the team.
• Settings — the project's name, key, and label management.

Project settings show the project's name and key, and link to label management for that project. What else is available here depends on your role's permissions within the organization.

Bugs, stories, tasks, and other work all live together as issues. When you create one, you give it a title and description, and set:

• Type — Bug, Story, Task, Epic, Improvement, or Test.
• Priority — Lowest, Low, Medium, High, Highest, or Critical.
• Assignee — who's responsible for it (optional).
• Story points — an optional size estimate.
• Due date — optional.
• Sprint — assign it to a Sprint now, or leave it in the Backlog.

Opening an issue shows everything associated with it, and lets you update:

• Status — moves the issue through your project's workflow.
• Labels — organize and filter issues within the project.
• Sprint and milestone assignment.
• Parent/sub-issue relationships, and links to related issues.
• Comments and a full history of changes made to the issue.
• An embedded Planning Poker card, if the issue needs estimation.

The Backlog lists a project's issues that aren't yet assigned to a Sprint and aren't done, sorted by priority. From the Backlog, an issue can be assigned directly to a Sprint if your role has Sprint-assignment permission.

The Board shows issues grouped by status, so you can see what's in progress at a glance. A List view is available as an alternative to the Kanban layout, along with a compact density option, for teams that prefer scanning a table.

Create a Sprint from a project's Sprints tab. A new Sprint starts in the Planned state. Assign issues to it from the Backlog, the Board, or the issue detail page.

• Planned — the Sprint exists and has issues assigned, but hasn't started.
• Active — the Sprint is underway. Starting it requires Sprint-management permission.
• Completed — the Sprint is finished. When you complete a Sprint, you write a short completion summary and choose what happens to any issues that weren't finished — roll them over into another Sprint, or leave them.
• Cancelled — a Sprint can be cancelled with an optional reason.

Open the issue you want to estimate and choose to start Planning Poker. This creates a session tied to that issue. A shareable room code lets others join the session directly, or they can find it from the project's Planning Poker tab, which lists sessions currently in progress.

1. Each participant privately picks a card from the estimation deck. Votes stay hidden — even from the facilitator — until the round is revealed.
2. The facilitator reveals the votes once everyone has voted.
3. If votes don't agree, the facilitator can start another round.
4. The facilitator finalizes the estimate — QAForgeHub suggests a value based on the votes, but the facilitator confirms it.
5. The finalized estimate is saved as the issue's story-point estimate, and the session closes.

A milestone groups issues working toward the same target. Assign an issue to a milestone from the issue detail page. Creating and managing milestones requires the appropriate project permission.

The Roadmap groups a project's milestones by status — In Progress, Planned, Completed, or Missed — so you can see progress toward each one at a glance.

A project report is a status update covering progress, Sprint status, milestones, risks, blockers, decisions, and next steps. Create one from a project's Reports tab, add items to it, and it stays a draft until you publish it.

• Reports can link directly to specific issues and Sprints.
• A report can be edited while it's a draft.
• Publishing makes the report visible to the rest of the project as a numbered version. Published reports can be archived, and archived reports can be restored.

• Free — up to 3 active projects and 5 members per organization.
• Pro — unlimited projects and members, billed per organization (monthly or annual).

Your first organization is on the Free plan with no payment required. Each additional organization you own needs its own Pro subscription and stays in a setup state — no projects, members, or workspace features — until that subscription is active. If you abandon checkout, the organization is not usable; you can return to its activation page later or remove it.

Pro is billed per organization, not per seat — the price doesn't change based on how many members you have, and members are never charged for being invited. It's available as a monthly or annual subscription; choosing annual billing is typically cheaper than paying monthly. Exact current pricing is shown on your organization's Billing page.

"One free organization" means one at a time, not one ever. If you later transfer ownership of your only organization away, you can create a new free one.

If an organization is above its plan's project limit — for example, after downgrading — nothing existing is removed or archived automatically. You just can't create new projects until you're back under the limit or you upgrade.

Only an Owner or Administrator can open an organization's Billing page — its plan, subscription status, and usage. Project Manager, Developer, Tester, and Viewer don't have access to organization billing data at all, whether from the navigation or by visiting the page directly.

From the Billing page, an Owner or Administrator can subscribe to Pro, and manage an existing subscription — including updating payment details or cancelling — through the billing portal.

Log in with your email and password. Log out at any time from the user menu in the top-right corner of the app.

Use "Forgot password" on the login page and enter your registered email address. QAForgeHub emails a one-time reset link directly to that address, and only you see it — you choose your new password privately; QAForgeHub support never receives the reset email or the new password you set.

If the reset email doesn't arrive, check spam first, then email support@qaforgehub.com for delivery troubleshooting. If you've lost access to your registered email address entirely, that's account recovery rather than an ordinary reset — contact support@qaforgehub.com for help. Support can never ask for your password, your reset link, an MFA code, or a recovery code — never send any of those, even if a message claims to be from QAForgeHub.

Every account can turn on two-factor authentication from Account settings. Enrolling shows a QR code to scan with an authenticator app; entering the 6-digit code it generates confirms enrollment and shows you a set of one-time recovery codes — save these somewhere safe, as they're shown only once.

• Once enabled, logging in asks for your authenticator code after your password.
• A recovery code can be used in place of your authenticator code if you lose access to it.
• You can regenerate your recovery codes at any time, which invalidates the old ones, or turn MFA off entirely — both require confirming your password.

For questions about your organization — your role, an invitation, or billing — start with your organization's Owner or Administrator; they can see and manage all of these for you directly inside QAForgeHub.

For account, billing, or platform issues your organization's Owner or Administrator can't resolve — a billing charge you believe is wrong, a service outage, or a suspected bug — email support@qaforgehub.com.

To report a security vulnerability, incident, or other concern that needs QAForgeHub's own involvement, email support@qaforgehub.com with "Security Report" in the subject, rather than opening a public issue. See the Security page for what to include in your report.