Project Members

QA Note nests Projects inside an Organization. Members join the organization first and are then assigned to projects. Seat billing is bundled at the organization level, so understanding when a project membership consumes a seat keeps day-to-day administration simple.

Organization vs Project

Organization members are a superset of project members — joining a project always requires being part of the parent organization first. You cannot share only a project to someone outside the organization. For external feedback, use the Widget instead.

Invitation methods

Email invites are valid for 24 hours. A seat is consumed at the moment the invite is accepted, not at send time. If your seat budget is full when an accept arrives, the recipient is shown a "buy one more seat" prompt before they finish onboarding.

Roles · permissions

Organization roles form a four-step hierarchy: Owner > Admin > Member > Guest. Project membership has its own three-step role (admin · member · guest).

An organization must always have at least one Owner. The last Owner cannot deactivate themselves or downgrade their role. Promote another member to Owner first to hand off ownership.

Project-level overrides (for example, inviting an outside collaborator as guest to a specific project) live under Project settings → Members.

Seat consumption

Inside an organization, active members = seats consumed. The same person assigned to ten projects still consumes only one seat.

Example: Pro plan with 3 seats

• Purchased seats: 3 (₩12,000/mo × 3 = ₩36,000/mo)
• Active organization members: 3 → at the cap
• Inviting a 4th member: blocked, with an inline "add 1 seat?" prompt that triggers a prorated charge on confirm
• Deactivating one member: seat count stays at 3. Seat counts only change from billing settings.
• Scheduling a seat decrease: takes effect at the next billing cycle. You can keep operating up to the existing limit until then.

The Solo plan is not seat-based. Up to 3 free members can collaborate; upgrade to Pro when you outgrow that limit.

Deactivation

Deactivation is not deletion. The member's data (issues authored, comments) stays intact, and only the following are blocked:

• Sign-in (dashboard · Extension · widget · API)
• Notifications (assignments, mentions, …)

Reactivating a deactivated member in the same organization restores their previous role and project memberships. Permanent deletion follows your data retention policy and is performed by an Owner separately.

Owners cannot be deactivated — transfer ownership first.

Invitation limits

Compare plans on the Pricing page.

Audit log

The following events are recorded to the organization audit log (Activity Log) and retained for 90+ days on Pro and above.

• Invite sent · accepted · expired
• Role change (Member ↔ Admin ↔ Owner)
• Member deactivation · reactivation
• API key issuance · revocation

Teams preparing for SOC 2 / ISO 27001 typically pair the audit log with the export feature. See the Audit log guide for details.

FAQ

Q. How do I expose a single project to an outside collaborator? A. Add them to the organization as a Member first, then drop them from every project except the one you want to share. For more isolated sharing, use a share link.

Q. Does removing someone from a project free up a seat? A. No. Seats are billed at the organization level. Project removal alone leaves the seat count untouched — schedule a seat decrease only after the member is deactivated at the org level.

Q. Who can use AI Fix and MCP? A. Anyone with the organization Member role or higher. Fair-use quotas apply at the organization level — see the AI Fix and MCP Server pages for limits.