You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/core-concepts/projects/manage-project-members.md
+56-47Lines changed: 56 additions & 47 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,18 @@
1
1
---
2
2
title: Manage project members
3
-
description: Add members to projects, assign roles, and configure access
3
+
description: Add members to projects, assign roles, configure default assignee and project lead, manage subscribers, and understand how teamspace memberships interact with direct project access.
4
4
---
5
5
6
-
# Manage members
6
+
# Manage project members
7
7
8
8
Manage who has access to your project and what they can do by adding members and assigning roles.
9
9
10
+
For background on the available roles, see [Member roles](/roles-and-permissions/member-roles).
11
+
10
12
**Prerequisites:**
11
13
12
-
- You must be a Project Admin or Workspace Admin to manage project members
13
-
- Users must be workspace members before they can be added to projects
14
+
- You must be a Project Admin or Workspace Admin to manage project members.
15
+
- Users must be workspace members before they can be added to projects.
14
16
15
17
## Add members to a project
16
18
@@ -29,27 +31,37 @@ Users must be workspace members before you can add them to a project.
29
31
2. Scroll to the **Members** section.
30
32
3. Click **Add member**.
31
33
4. Search for and select the workspace member.
32
-
5. Assign their role: **Admin**, **Member**, or **Guest**.
34
+
5. Assign their role: **Admin**, **Contributor**, **Commenter**, or **Guest**.
33
35
6. Click **Add**.
34
36
35
37
The member now has access to the project with the permissions defined by their role.
36
38
37
-
**Project roles:**
39
+
### Project roles
40
+
41
+
-**Admin** — Full project access including settings, member management, and all features.
42
+
-**Contributor** — Can create and manage work items, epics, cycles, modules, pages, and views. Can delete content they created themselves.
43
+
-**Commenter** — Can view all work items in the project and add comments and reactions. Can also create intake submissions.
44
+
-**Guest** — Limited access. Can submit intake forms and view, edit, and delete intake issues they created.
45
+
46
+
::: info Renamed roles
47
+
The role previously called **Member** is now called **Contributor**. Permissions are unchanged.
48
+
The previous **Guest view access** toggle has been replaced by the **Commenter** role. To grant view access plus commenting, assign the Commenter role.
49
+
:::
50
+
51
+
See [Permissions matrix](/roles-and-permissions/permissions-matrix) for the complete breakdown.
38
52
39
-
-**Admin** - Full project access including settings, member management, and all features.
40
-
-**Member** - Can create and manage work items, cycles, and modules (cannot change project settings).
41
-
-**Guest** - Limited view access (cannot create or edit).
53
+
### Workspace Guest restriction
42
54
43
-
See [Member roles](/workspaces-and-users/roles) for complete role permissions.
55
+
If you're adding a workspace Guest to your project, you can only assign them the **Guest** or **Commenter**role. Attempting to assign Admin or Contributor returns an error. This guardrail prevents external collaborators from being accidentally over-privileged.
44
56
45
57
## Change a project member's role
46
58
47
59
Update project member roles as responsibilities change.
48
60
49
-
1. Navigate to **Project Settings > Members & Teamspaces**
50
-
2. Find the member in the **Members** list
51
-
3. Click the **Role** dropdown next to their name
52
-
4. Select the new role (Admin, Member, or Guest)
61
+
1. Navigate to **Project Settings > Members & Teamspaces**.
62
+
2. Find the member in the **Members** list.
63
+
3. Click the **Role** dropdown next to their name.
64
+
4. Select the new role.
53
65
54
66
The role change takes effect immediately.
55
67
@@ -66,19 +78,23 @@ The member loses access to the project immediately but remains in the workspace.
66
78
67
79
**What happens when you remove a member:**
68
80
69
-
- They can no longer access the project or its work items
70
-
- Work items they created remain in the project
71
-
- Their comments and activity history are preserved
72
-
- They remain a workspace member (unless removed separately)
81
+
- They can no longer access the project or its work items.
82
+
- Work items they created remain in the project.
83
+
- Their comments and activity history are preserved.
84
+
- They remain a workspace member (unless removed separately).
85
+
86
+
::: info Removing workspace Owners and Admins
87
+
Removing a workspace Owner or Admin from a project removes the project membership record but does not restrict their access — they retain access to all project content via their workspace role.
88
+
:::
73
89
74
90
## Default assignee
75
91
76
92
Configure a default assignee to ensure all work items get assigned when created without an explicit assignee.
77
93
78
-
1. Navigate to **Project Settings > Members & Teamspaces**
79
-
2. Find the **Default Assignee** setting
80
-
3. Click the dropdown and select a project member
81
-
4. The setting saves automatically
94
+
1. Navigate to **Project Settings > Members & Teamspaces**.
95
+
2. Find the **Default Assignee** setting.
96
+
3. Click the dropdown and select a project member.
97
+
4. The setting saves automatically.
82
98
83
99
**How default assignee works:**
84
100
@@ -107,7 +123,7 @@ The project lead is the go-to person for questions about the project's execution
107
123
- Project Admin is a role with specific permissions.
108
124
- They can be the same person but don't have to be.
Project subscribers receive notifications for all work items in the project — status changes, comments, and updates. This is useful for project leads, managers, or stakeholders who need visibility across the entire project without being subscribed to individual work items.
113
129
@@ -123,18 +139,6 @@ To configure project subscribers:
123
139
124
140
Only project admins can manage project subscribers.
125
141
126
-
## Grant view access to Guests
127
-
128
-
By default, Guests can only see work items they've created through the Intake section. You can expand their visibility to all project work items.
129
-
130
-
1. Navigate to **Project Settings > Members & Teamspaces**.
131
-
2. Find the **Guest access** setting.
132
-
3. Toggle on **Grant guest users view access to all the project work items**.
This setting is project-specific. Enabling it in one project doesn't affect Guest permissions in other projects. Even with view access, Guests remain isolated to invited projects only.
137
-
138
142
## View project member activity <Badgetype="warning"text="Enterprise Grid" />
139
143
140
144
::: info
@@ -150,34 +154,39 @@ Track member actions like additions, role changes, and removals to maintain visi
150
154
151
155
The activity panel shows recent project member events:
152
156
153
-
-**Member additions** - Who added which members to the project and when.
154
-
-**Role changes** - Role updates with who made the change and when.
155
-
-**Member removals** - Who removed members from the project.
156
-
157
-
Each activity entry shows:
157
+
-**Member additions** — who added which members to the project and when.
158
+
-**Role changes** — role updates with who made the change and when.
159
+
-**Member removals** — who removed members from the project.
158
160
159
-
- The action taken
160
-
- Who performed the action
161
-
- When it happened (relative time like "6 days ago" or "3 days ago")
161
+
Each activity entry shows the action taken, who performed the action, and when it happened (relative time like "6 days ago" or "3 days ago").
162
162
163
163
This audit trail helps project admins monitor membership changes and verify that access permissions are correct. Activity is retained for project history.
164
164
165
165
## Leave a project
166
166
167
-
If you no longer need access to a project, you can leave it yourself. Click the … menu next to your own name in Project Settings > Members & Teamspaces and select Leave.
167
+
If you no longer need access to a project, you can leave it yourself. Click the … menu next to your own name in **Project Settings > Members & Teamspaces** and select **Leave**.
168
168
169
169
You'll lose access to the project immediately but remain in the workspace. If you need to rejoin later, a Project Admin or Workspace Admin will need to add you again.
170
170
171
+
::: warning Last admin protection
172
+
If you're the only Project Admin, you cannot leave the project. Promote another member to Admin first.
173
+
:::
174
+
171
175
## How users join projects
172
176
173
177
Users can become project members in two different ways, and understanding both helps you manage your project team effectively.
174
178
175
-
**Direct project membership** is where you specifically invite users to your project and assign them roles. These members have access only to the projects you've added them to, and you have full control over their permissions.
179
+
**Direct project membership** is when you specifically invite users to your project and assign them roles. These members have access only to the projects you've added them to, and you have full control over their permissions.
180
+
181
+
**Teamspace-based membership** happens automatically when your project is linked to a [Teamspace](/core-concepts/workspaces/teamspaces). All members of that teamspace automatically receive the role assigned on the teamspace-to-project link, making it ideal for teams that collaborate across multiple projects.
176
182
177
-
**Teamspace-based membership** happens automatically when your project is linked to a [Teamspace](/core-concepts/workspaces/teamspaces). All members of that teamspace automatically receive `Member` access to your project, making it perfect for teams that collaborate across multiple projects.
183
+
Users can have both types of access simultaneously. When this happens, Plane evaluates both grants — direct membership is checked first, and either source can grant the access.
178
184
179
-
Users can have both types of access simultaneously. When this happens, Plane automatically applies whichever role gives them higher permissions. For example, if someone is a `Guest` on your project but joins a linked teamspace, they're automatically upgraded to `Member` access. If they're already an `Admin`, they keep their `Admin` role.
185
+
For example, if someone is a `Guest` on your project but joins a linked teamspace whose link grants `Contributor` access, they get Contributor access to the project through the teamspace. If they're already an `Admin`, they keep their `Admin` role through their direct membership.
Copy file name to clipboardExpand all lines: docs/core-concepts/workspaces/members.md
+27-13Lines changed: 27 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,11 +3,13 @@ title: Manage workspace members
3
3
description: Add, update, and remove workspace members
4
4
---
5
5
6
-
# Manage members
6
+
# Manage workspace members
7
7
8
-
Keeping your workspace organized and secure is essential for smooth project management. Plane makes it easy to control who can access your workspace, what they can do, and how they collaborate with others.
8
+
Manage who can access your workspace and what they can do.
9
9
10
-
This guide shows you how to add members to your workspace, change their roles, and remove them when needed.
10
+
This guide covers inviting members, importing them in bulk, changing roles, removing members, and viewing audit history.
11
+
12
+
For background on the available roles, see [Member roles](/roles-and-permissions/member-roles).
11
13
12
14
## Invite members to your workspace
13
15
@@ -19,7 +21,7 @@ You can add members individually or in bulk using CSV import.
19
21
2. Click **Add member**.
20
22
3. In the modal:
21
23
- Enter the email address of the person you're inviting.
22
-
- Select their role: **Admin**, **Member**, or **Guest**.
24
+
- Select their role.
23
25
- To invite multiple people at once, click **Add another** and repeat.
24
26
4. Click **Invite**.
25
27
@@ -57,16 +59,21 @@ Email, Display Name, First Name, Last Name, Role
For backward compatibility, numeric role values still work: `5` for Guest, `15`for Member, `20` for Admin. We recommend using slugs.
76
+
:::
70
77
71
78
**Important notes**
72
79
@@ -130,9 +137,16 @@ Removing members doesn't change your seat count or billing. You must [remove sea
130
137
131
138
## Leave a workspace
132
139
133
-
If you no longer need access to a workspace, you can leave it yourself. Click the … menu next to your own name in Workspace Settings > Members and select **Leave**.
134
-
You'll lose access to the workspace and all its projects immediately. If you need to rejoin later, a Workspace Admin will need to invite you again.
140
+
If you no longer need access to a workspace, you can leave it yourself. Click the … menu next to your own name in **Workspace Settings > Members** and select **Leave**.
141
+
142
+
You'll lose access to the workspace and all its projects immediately. If you need to rejoin later, a Workspace Admin or Owner will need to invite you again.
143
+
144
+
::: warning Last admin protection
145
+
If you're the only Owner or Admin in the workspace, you cannot leave. Promote another user to Owner or Admin first.
Copy file name to clipboardExpand all lines: docs/core-concepts/workspaces/overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ Every workspace in Plane has two main components:
16
16
-**Projects**
17
17
Projects serve as the cornerstone for all activities within the product. You can create work items, assign tasks to members, and track progress for whatever you’re working on. If you envision your organization as NASA, each mission can be likened to a project. [Learn more here](/core-concepts/projects/overview).
18
18
-**Members**
19
-
Invite your teammates, collaborators, or managers to join your workspace. Each user gets a role, like Admin, Member, or Guest, to control what they can do. [Explore roles here](/workspaces-and-users/roles).
19
+
Invite your teammates, collaborators, or managers to join your workspace. Each user gets a role, like Admin, Member, or Guest, to control what they can do. [Explore roles here](/roles-and-permissions/member-roles).
0 commit comments