Team, settings & billing

Review invitation access before sending

Read the invitation role and Project-access preview before deciding to invite someone.

Reviewed

On this page

Review an invitation's role and Project scope before deciding to send it. The access preview helps you check that a future teammate would receive the access appropriate for their work in the intended organization.

Before you start

Confirm the workspace and your authority to manage team access. An organization Owner manages Admin access; ordinary organization administration has narrower team-management limits. Think about the person's actual task and which Projects they need, rather than choosing the broadest available access by habit.

Review the invitation

  1. Open Settings → Team in the intended organization.

  2. Open the invitation directory and expand Invite member.

  3. Inspect the Email field and the currently selected role before entering a recipient.

  4. Read Role matrix if you need help deciding which role fits the work. Compare that role with the selection shown in the invitation form.

  5. Read Invitation access preview. When it shows All Projects, consider whether that scope is appropriate for the teammate's responsibilities.

  6. Resolve any uncertainty about the recipient, role or Project scope before proceeding to an invitation decision.

Unsent invitation access preview showing Editor, All Projects and feature scope.

Unsent invitation access preview showing Editor, All Projects and feature scope.

Example with fictional data: Editor and All Projects in the invitation access preview.

Check the result

You understand the proposed access and can explain why it fits the person's responsibilities. Role and Project assignment are both relevant: a suitable role can still be too broad if it applies to more Projects than the person needs.

If a control is unavailable

Check the selected workspace and your team-management authority. Ask the Owner to review an Admin-level request. Keep the intended recipient and task clear when requesting that review, and avoid duplicate invitations while the access question is being resolved. After someone joins, effective membership and assignments should be checked against the agreed access.