Deleting Users may lead to broken references in a lot of documents.

[dting]

Since we use references to the User in a lot of documents. Allowing for destructive deletes of the user will lead to a lot of broken references.

One possible solution is instead of destructively deleting a User, the delete action could delete the User.google object, unset the User.assignment and set the User.role to deleted. This would effectively remove all access to the app for that User, while maintaining that User document referenced by other documents. This also allows a new User to be created by that google account for future access. It will be a new User with a different User._id.

[dting]

This type of delete would require a couple updates to the User api route that filters out deleted Users when listing all Users.