You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the recent introduction of the feature to delete admin users in #934, it is crucial to consider implementing a cascade delete mechanism for admin-related resources such as projects, documents, and changes.
Why:
Currently we only allows the deletion of admin users without any cascading effect on related resources, potentially resulting in orphan resources beyond the control of the admin. To ensure better resource management and data consistency, the introduction of cascade delete functionality is essential.
The text was updated successfully, but these errors were encountered:
Description:
Following the recent introduction of the feature to delete admin users in #934, it is crucial to consider implementing a cascade delete mechanism for admin-related resources such as projects, documents, and changes.
Why:
Currently we only allows the deletion of admin users without any cascading effect on related resources, potentially resulting in orphan resources beyond the control of the admin. To ensure better resource management and data consistency, the introduction of cascade delete functionality is essential.
The text was updated successfully, but these errors were encountered: