Toby Osborne

Hi, @Vinod Kumar Thanks for the reply. Would it not be possible (at least for Google Drive); to simply let Google's file permissions handle it. e.g. Sharing a vault with my client I would need to first share the folder (Via Google Drive), then they can get their own OAuth token, and point the vault to the in their own drive account. (This would also mean that if I decided later to revoke access I could just remove their permissions on Google Drive). With a little more code, it could be that Enpass verifies permission to the folder via the Drive API and gives the request access button if they don't. Please, Please, Please reconsider this. I love the idea of Vaults, but simply can't use them as they are now.

Firstly I love the new look and the new features but like @chribonn I can't use vaults for my use case; from a business perspective, I would like to make a vault for each client; unfortunately, I don't have 30 or so Google accounts to hand. I can understand that the vault name could change and so runs the risk of messing up the sync, perhaps just letting us choose where the file gets stored would work, that way we could just create subdirectories for each vault. Please add multiple vaults to sync with a single account.