Team Management
Learn how to manage workspace members, assign roles, track activity, and handle member status in Devpilot.
Team Management
Every workspace in Devpilot has its own team — a group of users who collaborate on the workspace's resources. The Team page gives you full visibility into who has access, what role they hold, and how they are using the workspace. This guide covers how to view, add, remove, and manage team members.
Viewing Team Members
Navigate to your workspace and select Team from the sidebar. The team member list displays all users associated with the workspace, including:
| Column | Description |
|---|---|
| Name | The member's display name and email address. |
| Role | The workspace role assigned to this member — Owner, Admin, or Member. |
| Status | The member's current state — Active, Pending, Suspended, or Inactive. |
| Joined | The date the member joined the workspace. |
| Last Active | The most recent time the member performed an action in this workspace. |
You can filter the list by role, status, search term, or last-active date range, and sort by the column of your choice.
Member Status
Each team member has one of four statuses:
The member has joined the workspace and can perform actions according to their role.
The member has an outstanding invitation but has not yet accepted. They do not have access to workspace resources until they accept. See Invitations.
The member's access has been temporarily revoked by an Owner or Admin. Suspended members cannot view or interact with workspace resources. Their role assignments are preserved, so access can be restored without re-inviting them.
The member is marked inactive — typically used when a member is no longer engaged with the workspace but their record is retained for audit history.
Adding Team Members
To add a new member, send an invitation via email. Only workspace Owners and Admins can invite members.
Open the Team Page
Navigate to your workspace and select Team from the sidebar.
Click "Invite Member"
Select the Invite Member button at the top of the team list.
Enter the Member's Email and Role
Provide the email address and select the role — Admin or Member. See Roles and Permissions for a detailed breakdown of each role.
Send the Invitation
Click Send Invitation. The invitee receives an email with a secure link. They appear in the team list with a Pending status until they accept.
For inviting multiple members at once, or to customize expiry, reminders, and messages, see the Invitations guide, which covers bulk invitation workflows.
Adding an Existing User Directly
If the person you want to add already has a Devpilot account, an Owner or Admin can add them directly to the workspace without an email invitation. From the invite form, select an existing user, pick a role, and they are added as an Active member immediately.
Changing a Member's Role
Workspace Owners and Admins can change the role of any existing team member, except for the Owner.
Locate the Member
On the Team page, find the member whose role you want to change.
Open the Role Selector
Click the member's current role or choose Edit from their action menu.
Select the New Role
Choose the new workspace role — Admin or Member. The Owner role cannot be assigned this way.
Confirm the Change
Click Save to apply the new role. The change takes effect immediately on the member's next request.
You cannot change the Owner's role through the team management interface, and you cannot remove the Owner.
Granting Resource-Level Access
In addition to the workspace role, you can grant members scoped access to specific servers, projects, or apps. Resource-level access uses a separate set of roles — admin, collaborator, or viewer — and applies only to the resource you select.
From a member's detail view, open Grant Access and pick the servers, projects, or apps you want to grant, along with the resource-level role. You can also apply a custom permission set (a reusable bundle of resource-level permissions). See Roles and Permissions for a full explanation of the permission model.
Removing Team Members
When a team member no longer needs access, you can remove them.
Find the Member
On the Team page, locate the member you want to remove.
Open the Action Menu
Click the action menu on the member's row and select Remove Member.
Confirm Removal
Confirm the action in the dialog. Their access is revoked immediately.
Removing a member does not delete any resources they created. Projects, apps, and servers they set up remain in the workspace and continue to function.
Suspending and Restoring Members
Instead of removing a member, you can suspend their access temporarily.
Suspending a Member
Open the action menu for the member and select Suspend. Their status changes to Suspended and they lose access to workspace resources immediately, but their role and access records are preserved.
Restoring a Suspended Member
Open the action menu for a suspended member and select Restore. Their status returns to Active, and they regain access according to their previously assigned role and resource-level permissions.
Bulk Operations
For large teams, Devpilot supports bulk operations so you can manage multiple members at once.
Bulk Role Change
Select multiple members using the checkboxes, then choose Change Role from the bulk actions toolbar and pick a new role. The change applies to every selected member. Devpilot validates the operation and reports how many updates succeeded, any failures, and warnings such as attempted changes to Owners.
Bulk Remove
Select multiple members and choose Remove to revoke access for everyone selected at once. The Owner cannot be removed.
Bulk Access Grant
Select multiple members and choose Grant Access to grant the same servers, projects, or apps to all of them in one step.
Bulk Permission Assignment
Select multiple members and choose Assign Permissions to apply a set of resource-level permissions across servers, projects, or apps to all selected members at once.
Bulk operations take effect immediately. Review your selection carefully, especially for removal and suspension actions.
Tracking Member Activity
The Team page includes activity tracking to help Owners and Admins understand how members are using the workspace.
Individual Activity
From a member's detail view, select View Activity to see a log of their actions, including deployments, resource changes, settings updates, invitations sent, and access events. You can filter by action type and resource type, and limit how many events you see.
Team Activity Overview
For a workspace-wide view, navigate to the Activity sub-page. This feed shows every action taken by every member, with filters for member, action type, resource type, and date range.
Access Requests and Audit Logs
Members without access to a specific server, project, or app can submit an access request from the resource page. Owners and Admins can review pending requests from the Team area, then approve (optionally granting the requested role) or reject them. Cancelled requests are also tracked.
All access grants, revocations, role changes, approvals, and rejections are recorded in the workspace's access audit log, including the actor, the target member, the resource, before/after roles, and context such as IP address and user agent.
Best Practices
- Assign the least privilege needed — give each member the minimum workspace role and resource access required for their work.
- Use resource-level access for scoped collaboration — keep most members on the workspace-level Member role and grant them specific servers, projects, or apps instead of broader access.
- Audit regularly — review the team list and audit log periodically to remove members who no longer need access.
- Use suspension for temporary changes — prefer suspending over removing when the access change is temporary. This avoids the need to re-invite and reconfigure the member later.
- Investigate via the audit log — during incidents, use the audit log and per-member activity view to trace who did what and when.