Config with Centralized Policy

Feature name

Config with Centralized Policy

Feature function

I would like to request options be enabled to configure options via enterprise policy, at least for the key functions like setting a custom server address, but ideally all of them.

Something like this could be a useful functionality to use. Adding policy support to your extension | Firefox Extension Workshop

  • What will this feature do differently?

In environments with a manged policy, this will allow the extension to be configured and managed instead of giving the user a browser with the extension installed but unconfigured.

  • What benefits will this feature bring?

This will allow users of managed systems to use a new system and simply need to type their credentials, not configure the extension on first use. It will also allow the IT department to tune the extension to meet their needs.

Ideally it would also be useful to provide two config modes for each config key: a sane default setting (perhaps called “unlocked”) in which the extension has a config option set, but the user can modify it, or a forced setting (perhaps called “locked”) in which the extension has a config option set and the user is unable to modify it. This will allow the maximum flexibility for IT department users to set both helpful default the user can change, but also set options which they don’t want the user to be able to modify.

Hello @Conduit6914 and welcome to the forums,

Have you seen

As it may assist you to deploy the browser extension with managed devices.

Though I do like the idea of possibly a “locked” and “unlocked” browser extension as you mentioned. I think that could be a good addition to those IT teams who need to lock down things a bit tighter.

Hello @cksapp ,

Thanks for the quick response. Yes, I am familiar with that page, and I’m already making use of that functionality, perhaps I should have noted that in my initial response. This feature request is specifically targeting at being able to configure the extension after it’s installed, by being able to set config options centrally, either locked or unlocked.

In my particular case, it’s especially a pain point as we’re selfhosting, so we need to have users enter our bitwarden server URL, which leads to confusion when they try to enter their credentials without doing that. If there was only one config option the dev team would be willing to move to this sort of option, the server URL seems like a really good choice (though I’d love the ability to adjust any config option in the interface programmatically).

Happy to discuss more if you’d like.

My apologies I posted that help article but thought it contained some other information.
You are correct the previous article does not go into setting centralized settings, this article should help further for automating the deployment of your self-hosted URL

You are quite right. I missed that in my previous pass reading through that, thank you!

I would still love the other options, but that certainly does make it easier.