Project members

Every FoxPlan project brings together a team whose access is governed by a role. The role determines what a member can see and edit within the project. Choosing roles carefully is key to securing your data while letting everyone work efficiently.

Adding or managing members

Member management happens on the project's Definition & Members screen, Members tab.

1. Open the project, then the Definition & Members menu
2. Go to the Members tab
3. Click "+ Add a member"
4. Select a person already present in the workspace
5. Assign them a role (see below)
6. Save

Who can manage members?

Only a Project Admin can add, remove or change member roles. A Project Leader sees the Definition & Members screen in read-only mode (see the permissions table below).

The different project roles

FoxPlan distinguishes four roles at the project level, from the broadest to the most restricted.

🛡️ Project Admin

The most complete role. The Project Admin has full control of the project:

• Edit the project definition (dates, type, advanced settings, budget)
• Manage members: add, remove, change roles
• Edit planning, risks, budgets, project card
• Delete or duplicate the project

This is typically the role of the manager who created the project or owns its governance.

👤 Project Leader

The day-to-day operational role. The Project Leader drives execution but does not handle governance:

• Full editing of planning, tasks, risks, budgets, project card
• Read-only on the Definition & Members screen: they cannot edit the project definition nor manage the member list

Heads-up

The wording can be confusing: it is the Project Admin who holds administrative rights (including member management), not the Project Leader. The Project Leader has all business rights on the project, except on the Definition & Members screen which stays read-only for them.

👁️ Reader

The consultation role. The Reader can see everything but change nothing:

• View planning, budgets, risks, reports
• No write action anywhere

Ideal for a sponsor, a client or a stakeholder who needs to follow progress without intervening.

🧩 Resource

The contributor role. A Resource is a person assigned to project tasks:

• View the project and their own assignments
• Track progress on their tasks (depending on workspace configuration)
• No edit access to the project structure

Permissions summary table

Role	Definition & Members	Planning / Tasks	Budgets	Risks / Card	Manage members
Project Admin	✅ Edit	✅ Edit	✅ Edit	✅ Edit	✅ Yes
Project Leader	👁️ Read-only	✅ Edit	✅ Edit	✅ Edit	❌ No
Reader	👁️ Read-only	👁️ Read-only	👁️ Read-only	👁️ Read-only	❌ No
Resource	👁️ Read-only	👁️ Read-only¹	👁️ Read-only	👁️ Read-only	❌ No

¹ A Resource can update progress on their own tasks if the workspace allows it.

What about the workspace level?

The roles above apply project by project. There are also workspace-level roles (Administrator, Manager, Contributor, Member) that govern global access and project creation. They are described in the Settings section.

Good habit

Assign the most restricted role that still lets each person do their job. You can always broaden access later; tightening it afterwards is trickier.