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
Users who frequently access encrypted vaults may encounter situations where they need to ensure the integrity of their encrypted files without the risk of accidental modifications or deletions. By introducing a read-only mode unlock option, users can access their vaults while preventing unintended alterations to their encrypted data.
A user mentioned as an example that they fill a vault automatically via the Desktop app. The vault is basically used as an archive. In that case, it would make sense to access this particular vault in read-only mode.
Considered Alternatives
No response
Anything else?
The Desktop app already has a read-only mode option in the vault options (if the virtual drive technology supports it). This shouldn't be too hard to implement, since we already have a read-only mode option in the free version.
The text was updated successfully, but these errors were encountered:
Please agree to the following
Summary
Add read-only mode option in the vault settings.
Motivation
Users who frequently access encrypted vaults may encounter situations where they need to ensure the integrity of their encrypted files without the risk of accidental modifications or deletions. By introducing a read-only mode unlock option, users can access their vaults while preventing unintended alterations to their encrypted data.
A user mentioned as an example that they fill a vault automatically via the Desktop app. The vault is basically used as an archive. In that case, it would make sense to access this particular vault in read-only mode.
Considered Alternatives
No response
Anything else?
The Desktop app already has a read-only mode option in the vault options (if the virtual drive technology supports it). This shouldn't be too hard to implement, since we already have a read-only mode option in the free version.
The text was updated successfully, but these errors were encountered: