cryptomator
Delete vaults
Please agree to the following
- [X] I have searched existing issues for duplicates
- [X] I agree to follow this project's Code of Conduct
Summary
As a vault owner, I would like to be able to delete it.
Motivation
Time has shown that Hub users create various test vaults at the beginning to get to know Hub, which they then find annoying. Archiving is obviously not enough for some people.
However, we should link deletion to a "hurdle" so that it doesn't just happen accidentally and people are aware of the consequences. For example, a user could have to enter the recovery key during the deletion process.
Considered Alternatives
No response
Anything else?
No response
In my opinion, a proven hurdle is having to enter the name of the entity a second time for destructive actions. With GitHub, for example, I have to type the name Case-Sensitive again to delete the repo "Cryptomator/Repo123". Alternatively, I would also set the requirement that only empty vaults can be deleted.
I like the idea of entering the recovery key. Since we have something like that, we should use it.
Alternatively, I would also set the requirement that only empty vaults can be deleted.
We can't check that because Hub doesn't know about the contents of a vault.
