I’m seeking some clarification on the Delete User API endpoint, as it appears to work differently in practise than what is stated in the documentation.
The Delete User article also covers the same information as the Swagger docs. They state:
if the deleteAll parameter is set to true, all personal data (i.e. profile, photos, images, and files), message channels, posts and comments of the user will be deleted.
When I set the deleteAll parameter to true when deleting a user, I am seeing different behaviour to what should be happening:
The deleted user’s posts are removed, but their comments and replies are still visible (and their display name is now shown as “Deleted user”)
Additionally, when a new user joins the community after the user has been deleted, they can see the posts and comments that the deleted user made - the very same posts that existing users cannot see any more!!
Please can you clarify what flags I should be using to completely remove a user from Amity?
We need to do this when anonymising users due to GDPR regulations.
Hello @Baz, After running tests, we’ve confirmed that the delete user API is functioning properly. All relevant data, such as posts and comments, were deleted and are no longer returned in API responses.
To assist in troubleshooting, please forward your full cURLs to our support team at: support.asc@amity.co.
Hello, you can adjust the filter to exclude deleted posts/comments.
includeDeleted - Deletion filter. When the boolean is set to true, it retrieves both deleted and non-deleted posts. Conversely, when set to false, only non-deleted posts are returned. The default state of the boolean is false. Additionally, it excludes all deleted posts (both soft and hard deleted posts) not owned by the logged-in user. Community moderators have visibility of soft-deleted posts in the community feed, while self-users can see their own soft-deleted posts in their user feed.