Skip to main content
Project members table with invite action and member status badges
Use this page to manage who can work inside this specific project.

Important: Project access should match current work. Remove stale access before it becomes a security or ownership problem.

Questions this page should answer

  1. Who currently has access to this project?
  2. Which members are pending vs accepted?
  3. How should I scope permissions per person?

Before you use this page

  • In the app, open Project settings and select Members.
  • Check member seat capacity if invites are blocked.
  • Confirm whether changes should be project-only or organization-wide.

What this page controls

  • Project member list (Email, Role, Status, Actions).
  • Invite flow for adding members to this project.
  • Permission editing dialog for project-scoped feature/settings access.
  • Remove member from project action.

How to use this page

Invite with scope in mind

Add only users who need this project. If the email belongs to an already accepted workspace member, their project permissions update immediately. They do not receive a new invitation or need to use the Join screen again. For users who have not yet accepted workspace membership, verify that their status changes from Pending to Accepted. They must sign in with the invited email address and accept the workspace invitation before opening project pages. The Join screen offers Accept invitation and Decline; see Accept or decline an invitation for the steps and screenshot. For the full invite and permission model, use the detailed guide in Organization Members (role behavior, project assignment, and None / View only / Full scope definitions for each permission).

Invite from this project

The project Members invitation dialog is scoped to the current project. Review its name and project permissions. It does not offer unrelated projects or organization-setting permissions. To grant broader access, use Organization settings → Members.
Project-scoped invitation dialog showing current project permissions
Choose a project permission preset, then review the individual scopes before sending. See permission presets for the available starting points. Adding an accepted workspace member updates this project’s access immediately; a new workspace member must accept the invitation.

Edit permissions at project scope

Use the edit permissions action to control this project’s feature/settings access without changing all organization access.

Keep the list operationally clean

Remove members who no longer need project access to reduce risk and noise.

Quick weekly checklist

  1. Clear stale pending invites.
  2. Review elevated project permissions.
  3. Remove contributors no longer active on this project.

What to fix first

Team routine

  1. Weekly: clear pending invites and remove stale contributors.
  2. Monthly: review elevated permissions.
  3. After role changes: confirm project-level scope still matches the user’s work.

Keep in mind

  • Project membership is narrower than organization membership.
  • Seat limits can still impact invite operations.

Where to go next