Skip to main content
DELETE
/
v1
/
user
/
team
/
member
Delete Team Member
curl --request DELETE \
  --url https://api.projectdiscovery.io/v1/user/team/member \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '{
  "email": "<string>"
}'
{
  "message": "<string>"
}
Remove a member from your team workspace, revoking their access to all team resources including scans, assets, vulnerabilities, and configurations. This endpoint immediately terminates the member’s access to the team.

​
Use Cases

  • Employee Offboarding: Remove access when team members leave the organization
  • Access Revocation: Immediately remove unauthorized or compromised accounts
  • Project Completion: Remove temporary members after project-specific work concludes
  • Security Incidents: Quickly revoke access during security investigations
  • Team Restructuring: Remove members during organizational changes

​
What Happens When You Delete a Member

Immediate Effects:
  • ✅ Member loses all access to team workspace
  • ✅ Cannot view scans, assets, or vulnerabilities
  • ✅ Cannot create or modify team resources
  • ✅ Removed from team member list
  • ✅ Cannot access team API keys or integrations
What is Preserved:
  • 📝 Audit logs showing member’s historical actions
  • 📝 Scans and assets they created remain in the team
  • 📝 Their user account (outside the team) remains active
The member’s email must be provided to identify who should be removed. You cannot remove the team owner through this endpoint.

​
Important Considerations

Immediate Access Revocation: This action takes effect immediately. The member will lose access to all team resources without warning. Consider communicating with the member before removal if appropriate.
Cannot Remove Owner: The team owner cannot be removed through this endpoint. To change team ownership, you must transfer ownership first, then the previous owner can be removed.

​
Best Practices

  1. Timely Removal: Remove access promptly when no longer needed
  2. Documentation: Maintain records of who was removed and why
  3. Transfer First: Ensure critical work is transferred before removal
  4. Audit Trail: Review member’s activity before removal for compliance
  5. Communication: When appropriate, inform the member of pending removal
  6. Verify: Confirm removal was successful and access is revoked

​
Re-Adding Members

If you need to re-add a member after removal:
  • They must be invited again using the “Add Team Member” endpoint
  • They will need to accept a new invitation
  • Their previous role and permissions are not automatically restored
  • Consider their historical context when assigning new role
Instead of removing and re-adding members, consider temporarily changing their role to “Viewer” if they might need access again in the future.

Authorizations

​
X-API-Key
string
header
required

Headers

​
X-Team-Id
string

Retrieve the Team ID from: https://cloud.projectdiscovery.io/settings/team

Body

application/json
​
email
string
required

Response

Example response

​
message
string
required