[GH-ISSUE #2299] Option to soft-delete users and serviceaccounts from database #4582

Open
opened 2026-08-05 00:58:31 -04:00 by saavagebueno · 1 comment
Owner

Originally created by @mohamed-essam on GitHub (Jul 22, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2299

Is your feature request related to a problem? Please describe.
Activity page shows unknown@unknown for all deleted users, this affects the ability to trace audit accurately to any deleted user or service account.
This also causes management server logs to be flooded with entries like this

2024-07-22T08:20:26Z WARN [userID: 3e424766-3930-438c-8f78-d534af4933c9, context: HTTP, requestID: 921f8bd3-c6b5-4471-9979-8d6a27f8f6f1, accountID: cq2kl20pcgjc73c56jmg] management/server/http/events_handler.go:84: failed to resolve email for initiator: 44d8fdcb-90c8-41e8-95f7-5c42f0c0e841

Describe the solution you'd like
Users and service accounts should be soft deleted from the database with a flag, so it would still retain information about them. This should still be controllable with a flag in management service so it would adhere to GDPR and similar laws when needed.

Describe alternatives you've considered
N/A

Additional context
N/A

Originally created by @mohamed-essam on GitHub (Jul 22, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2299 **Is your feature request related to a problem? Please describe.** Activity page shows unknown@unknown for all deleted users, this affects the ability to trace audit accurately to any deleted user or service account. This also causes management server logs to be flooded with entries like this ``` 2024-07-22T08:20:26Z WARN [userID: 3e424766-3930-438c-8f78-d534af4933c9, context: HTTP, requestID: 921f8bd3-c6b5-4471-9979-8d6a27f8f6f1, accountID: cq2kl20pcgjc73c56jmg] management/server/http/events_handler.go:84: failed to resolve email for initiator: 44d8fdcb-90c8-41e8-95f7-5c42f0c0e841 ``` **Describe the solution you'd like** Users and service accounts should be soft deleted from the database with a flag, so it would still retain information about them. This should still be controllable with a flag in management service so it would adhere to GDPR and similar laws when needed. **Describe alternatives you've considered** N/A **Additional context** N/A
saavagebueno added the feature-request label 2026-08-05 00:58:31 -04:00
Author
Owner

@nazarewk commented on GitHub (Apr 23, 2025):

@mohamed-essam any idea whether this is still the case with the latest NetBird versions?

<!-- gh-comment-id:2825002071 --> @nazarewk commented on GitHub (Apr 23, 2025): @mohamed-essam any idea whether this is still the case with the latest NetBird versions?
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#4582