Closed ZhakalenDk closed 5 months ago
Currenly, the option of suspending a user is missing from our ER diagram and entities. Should we still add this?
If yes, when, how and why should the IsSuspended
flag be set?
Currenly, the option of suspending a user is missing from our ER diagram and entities. Should we still add this? If yes, when, how and why should the
IsSuspended
flag be set?
Good question 🤔 Maybe we could just use the soft delete feature to simulate this? And just "undelete" the account if a suspension is lifted? 🤷
Maybe. However, I had the impression that a suspended user would still be able to login to download already purchased content - but unable to do anything else within the app(?). Putting a deleted flag on their account would prevent them from doing that. 🤔
Yea. True 🤔 Should we ditch the suspension featuere or implement it?
If we implement it we would need to have a flag, I guess. Or and AccoutStatus field that can hold; Active, Deleted, Suspended?
Hmm, we could wait for a bit to get the core parts of the application running first. But for when we would like to implement it; how about if we added another AccountType for a suspended user?
I think that could work fine, actually. Especially because we, by doig that, can prohibit access to several things, including subscribtion libraries 👌
What's @jeongoks input on this?
Adding it as another AccountType sounds like a good plan.
users
users/{id}
users/{id}/books
users/{id}
users/{id}
users/{id}/suspend