[Feature Requests] Introduce "Footguns" #5791
senpro-ingwersenk
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
|
Well, that The current I am in the process of checking the differences between Vaultwarden and upstream in how we handle the API Calls, and what we return etc... Which might help me finding issues we currently have in regards to the roles, collections and groups, but that is currently on-going. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I got this idea after being poked by my co-workers that assigning permissions to users/groups on collections in orgs no longer worked (#5581) as it used to. Since that feature is technically part of the BitWarden Web UI, of which Vaultwarden uses a light modification, the only "real" place to add Vaultwarden-specific tools would be
/admin. And since these very specific utilities might or might not conflict with Bitwarden in some way, they're footguns. :)The first utility I would like to request here is to allow a user to check the old "full-access" field as mentioned in #5581 (reply in thread) . For context:
Clicking through all of that is a bit of a nightmare ;) We use a standart set of collections for each org, as they represent a customer we work with. Vaultwarden manages the sensitive information, Outline the documentary ones. The structure is standardized in the company I work at.
Hence, having a bit of batch-processing, knowing that it might conflict with Bitwarden, would be very helpful.
Thank you and kind regards!
Beta Was this translation helpful? Give feedback.
All reactions