How project scoping works

A project's team is separate from your full organization team. Only organization members can be added to a project, and only members already on the project appear in project-specific selectors such as assignment and team filters.

• Organization membership decides whether someone can potentially be added.
• Project membership decides whether they can access that specific project.
• Removing someone from a project removes their project access until they are added back.

Add members to a project

1. Open Project Settings: From the project, open Project Settings and go to the Team tab.
2. Click Add Member: Use Add Member to open the project team modal.
3. Select organization members: Search for one or more organization members who are not already on the project.
4. Confirm the add: TaskP3 adds them to the project as regular members first.

Project admin vs member

Inside the project team list, each project member is marked as either Admin or Member. Project admin is a project-level setting stored on that project membership record.

• Newly added members start as project members, not project admins.
• An organization admin can toggle a project member between Member and Admin.
• TaskP3 prevents the last project admin from being demoted without preserving admin coverage.

What happens when you remove someone

Removing a project member can trigger extra safeguards so the project is not left in a broken state.

• If the person still has assigned tasks, TaskP3 asks you to reassign those tasks first.
• If the person is the last project admin, TaskP3 asks you to choose a new project admin before removal completes.
• If you remove yourself, you lose access immediately and must be added back by an admin.

Good practices for scoping

• Keep project membership limited to people who actively need access.
• Grant project admin only to the people who should oversee that project's team and continuity.
• Before removing someone, decide who should take over their assigned tasks.