Members & invitations

A project's team is made of members with roles. This page covers how people join and leave; for what each role can do, see Roles & permissions.

Team size limits

The maximum team size depends on the project owner's plan (never on the inviting member's plan):

The owner counts toward the limit. Pending invitations also reserve seats: with a Plus plan and 2 members, you can only have 1 pending invitation at a time.

What happens after a downgrade

Members over the new limit are not removed. Instead, the most recently joined members beyond the cap lose access to the project until the owner upgrades again. The oldest members and the owner keep working normally.

Inviting members

Inviting requires the team.invite permission and the project owner being on the Plus plan or higher. Two ways to invite:

By email

• The invitee receives an email with an acceptance link.
• The invitation expires after 7 days.
• Only the invited email address can accept it: the invitee must sign in (or register) with a matching account.
• You cannot send a second invitation to an email that already has a pending one, or to someone who is already a member.

By shareable link

• A link invitation works for anyone who opens it, with no email restriction.
• Same 7-day expiry.
• No usage cap on the link itself, but every acceptance is checked against the team size limit, so a link cannot overflow your plan.

In both cases you pick the invitee's role at invite time. The Owner role can never be granted through an invitation.

Pending invitations are listed in the team settings (permission team.view), where they can be copied or revoked (team.invite). Revocation stays available even if the project has been downgraded below Plus, so you can always clean up.

Removing members

Removing requires the team.remove permission, with two hard rules:

• The owner cannot be removed, by anyone.
• An admin cannot remove another admin.

When a member is removed, their ticket assignments are cleared and their notifications and read states for the project are deleted. The tickets themselves, and every message the member wrote, are preserved.

Leaving a project

Any member can leave a project from the team settings, except the owner. Leaving triggers the same cleanup as a removal. An owner who wants out must delete the project instead.

Changing roles

Only the project owner can change a member's role. The owner role itself can neither be reassigned to someone else nor taken away: ownership is not transferable.

The owner

The owner is the account that created the project:

• Bypasses every permission check: the owner can always do everything.
• Counts as a team member.
• Cannot be removed, cannot leave, and cannot hand over ownership.
• The owner's subscription plan determines the project's features and limits for the whole team (see Plans & limits).