Is there a way for a global config for the desktop app on Linux?
On the following help page it’s only explained how to do per user: Configure Clients Centrally | Bitwarden Help Center
But I want to set the base url system wide.
PS: Why was this post flagged as spam? It’s a real unsolved question!
Hi @localhost and welcome to the community forums 
The forum system automatically flagged your posts as spam:
This new user tried to create multiple posts with links to the same domain. All posts from this user that include links should be reviewed.
You only signed up a couple of hours ago and have posted and created multiple topics including links. I have restored your posts.
Regarding your original question:
As explained in the help article, you posted, the client-specific data.json is edited and then used as a template to get re-distributed via other software deployment solutions. For example, jamf or other MDM solutions that work on Linux.
If this is meant to be done once, on one machine, then you can enter the environment URL(s) in the desktop client and these will be persisted for future use. More info on that can be found here: Connect Clients to your Instance | Bitwarden Help Center
Kind regards,
Daniel
That’s not the way global config works. Usually you have a config file in /etc/ (for example /etc/bitwarden/data.json). Then the application will take that config first and if the user have a userspecific config file, overwrite the changed config to the user specific value. Some application additionally allows to lock options that can not be overwritten from the user.
That’s the right way a business application works.
Is there support for that?
Hi @djsmith85
Even though this thread is almost a year old, there are companies out there who rely on a global config like @localhost requested.
It’s a pain for our config-management system, to deploy user-based configs in /home/user/.config/Bitwarden each time a new users logs onto this PC.
A global config like in /etc/Bitwarden/data.json to just configure the Self-hosted instance’s url would already help us a ton.
Please have a look into this.
If you need more information, I’m happy to help.
Another article about self-hosted URL information not being entered automatically for the user’s deployment. I’m beginning to think this isn’t possible.
The documented instructions for editing data.json are, IMHO, incomplete and/or not well thought out.
For one thing, data.json doesn’t exist on macOS devices until after the first time the end user opens the desktop client. And the note to use environmentUrls doesn’t link to any relevant supporting documentation on what that means or how to employ it.
I’d love to see Bitwarden provide a plist file that admins can use to generate system profiles for distribution by their MDM. I’ve not used JAMF so I can’t really speak to how it applies there, but the phrasing:
use your endpoint management solution of choice (like Jamf) to deploy the pre-configured Desktop app as a template.
Is utterly meaningless in all the MDM solutions I’ve tested.
I’m also joining in on this request 
Please create a functional way to distribute the app through MDM like Jamf with configured custom server and other settings. Ideally implement Managed App Configuration for macOS.This is something the app desperately needs. In our company, we use Vaultwarden by default, but the configuration of apps requires a lot of manual work and it may force us to switch to something else…