For many reasons, an user could become disabled.
It could happen:
- after a certain amount of warnings
- because of inactivity pruning #32
- because an user want to left the network ?? (is it the same thing)
But what does it mean to be disabled ?
- can't access sharable
- can't create sharable
- can't be contacted
- can't invite
So the user can still connect read the rules, and maybe later, contact staff.
What to do with already existing sharable ?
There are two cases:
- When the disabled user is the only manager
- this should be considerate as un-contactable, so impossible to be interested in.
- this mean sharable using contact method 1 are still working
- When there are onther non-disabled users
- the sharable should remain as contactable if at least one contact exist.
Is disabled the same thing as deleting an account ?
Account should never be totally deleted. As there is often this logic of one account / user / lifetime. But it is not for every purpose. Maybe this could be a global parameter. accountRealDelete (bool)
. Or, allow or not user to leave with no traces.
This is related to the question: can user delete sharables ? This is interesting for archive purpose.
After all, I think the solution may be to ask the leaving user if he or she'd like to delete all it's history or not. This could be a parameter allowUserDeleteHistory (bool)
. The most problematic deletion seems to be validations.