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
There would need to be stages of warnings for this, but for users to be able to manage their accounts effectively, they need a way to at least archive work, so their workspace isn't just always full of all the work they have ever done using our service.
The text was updated successfully, but these errors were encountered:
One question which comes to mind: do we leave any remnant of the project in our database, such as a marker saying "there was a project but it was deleted". This doesn't need to be visible to the user but may help us.
In terms of protecting the user against accidental deletion, a common thing you see is:
Are you sure? deleting this project will delete all associated sims, graphs, builds and deployments. This action can not be undone:
We list them with date, ID status etc.
User enters Y or N depending on their choice. (I think Peter's suggestion of type the name of the project is better though)
This will be better when we can give sims, builds etc names/tags rather than just the UUID as they will be able to tell what they are deleting more easily.
There would need to be stages of warnings for this, but for users to be able to manage their accounts effectively, they need a way to at least archive work, so their workspace isn't just always full of all the work they have ever done using our service.
The text was updated successfully, but these errors were encountered: