Project Members
Project members are the employees attached to a project. You choose them with the Add Project Members multi-select on the project create/edit form, so the people who need to work on a project are attached to it from the moment it exists.
Project members are employees. The client side of a project is handled separately by the project's Client field, which links the project to a client record — see Clients.
Who can use it
Anyone whose role grants permission to create or edit projects can set project members, because the member selector lives on the project form itself. What a member can then do inside the project is decided by their own role in Roles & Permissions, not by their membership alone. Roles with view-only project and task permissions cannot modify projects or tasks even when they are members.
Prerequisites
- A project to work on, or a new one you are creating. See Creating a Project.
- The people you want to add must already exist as employee records. See Adding Employees.
- Permission to create or edit projects, granted through Roles & Permissions.
How to Access
- Projects list:
/account/projects - Add Project form:
/account/projects/create - Roles & Permissions (to check what a member can do): Settings → Roles & Permissions
- Notification Settings (Slack delivery of assignment alerts):
/account/settings/notifications
Adding members when you create a project
- Go to
/account/projects/create. - Fill in the project details — Short Code, Project Name, Start Date, Deadline, Project Category, Department, Client, Project Summary, Notes.
- In the Add Project Members field, select the employees who should be on the project. The field is a multi-select, so you can pick several people in one pass instead of adding them one at a time.
- Set the remaining options you need — Label, Create Public Project, Public Gantt Chart, Public Task Board, "Task needs approval", Currency, Project Budget, Hours Estimate, the project-progress calculation method, "Allow manual time logs", "Enable Mindboard", and "Send task notification to client".
- Save the project.
Changing members on an existing project
Open the project and edit it, then adjust the Add Project Members selection — add the people you want and deselect the ones who should no longer be on the project. Save to apply the change.
Because member changes are part of the project form, they are saved together with any other edits you make in the same pass. If you only want to change membership, change nothing else before saving.
Members vs. the project client
The project form also has a Client field. That is separate from project members: it links the project to a client record rather than adding someone to the internal team. Client-facing visibility is controlled by the project's own toggles — Create Public Project, Public Gantt Chart, Public Task Board and Send task notification to client — not by the member list. See Clients.
Effect on other features
- Notifications: Project assignment and task assignment are among the events PMSuite can notify on. If your company has connected Slack under Settings → Notification Settings → Slack, project- and task-assignment events can be delivered to your Slack channel alongside the in-app bell. See Slack Integration.
- Permissions still apply on top of membership: Being a member does not override a role. What a member can view or edit on the project — including the budget and earnings figures on the Overview panel — is still decided by their role's permission level for that module and action. See Project Overview.
- Clients see less than members: The Gantt chart and task board are only visible to the client if Public Gantt Chart / Public Task Board are enabled on that project — both are off by default — so a client's view is not the same as a member's.
- Discussions and notes: Members can be mentioned in project discussions, which produces a Project Mention notification for that person. See Discussions.
Limitations
- Membership is edited on the project form, not from a standalone member console. There is no separate "member management" screen with per-row add/remove buttons. Workaround: edit the project and change the Add Project Members multi-select — it accepts multiple changes at once, so a single edit can cover a whole reshuffle.
- Membership alone does not grant capability. A member with a restricted role still cannot do things their role forbids, which can look like "the project isn't working for them." Workaround: check Settings → Roles & Permissions for that user's role. Permission levels are None, Added, Owns, and All — pick the level that matches what they need.
- Employees only. Client-side people cannot be added through the member selector. Workaround: set the project's Client field to the right client record and use the project's public toggles (Create Public Project, Public Gantt Chart, Public Task Board) to give them the visibility they need — see Clients.
Troubleshooting
A person doesn't appear in the Add Project Members list.
The selector draws on employee records. Confirm the person exists and is active under /account/employees.
Someone was added but says they still can't see or do something on the project. This is almost always a role/permission issue rather than a membership issue. Check Settings → Roles & Permissions for their role, then have them log out and log back in — permission changes do not always take effect in a session that is already active.
A member can't see the project's budget figures. Budget and earnings figures on the Overview panel follow the user's role permissions, not their membership. Check the role's permission level for the relevant module in Settings → Roles & Permissions, then have them log out and log back in.
Assignment notifications aren't reaching Slack.
Open /account/settings/notifications → Slack tab, confirm Status is enabled and a valid Slack webhook URL is saved, confirm the project/task assignment events are checked, and use Send Test Notification to verify delivery. Note that PMSuite → Slack is one-way notification delivery.