DBeaver Documentation


Admin Preference Restrictions


This guide outlines the steps for enhancing security and control in DBeaver by restricting specific functionalities.

For Windows, Mac, and Linux, restrictions in the dbeaver.ini file can be implemented, while Windows users can also leverage the Registry for additional control.

Setting up restricted functionalities

Follow the appropriate steps based on your operating system and preference.

Modifying the configuration file

  1. Navigate to the directory containing the dbeaver.ini file.
  2. Use a text editor to open the configuration file.
  3. Add settings from the table below based on desired restrictions.
  4. Save the edited file.
  5. Restart DBeaver to apply changes.
System control variables
Name Type Default value Allowed values Description
-Dpolicy.data.export.disabled Boolean false true, false Restricts ability to export data from databases.
-Dpolicy.software.install.disabled Boolean false true, false Blocks ability to install new software and access the Eclipse marketplace.
-Dpolicy.software.update.disabled Boolean false true, false Prevents ability to check for DBeaver updates.

Using Windows Registry

  1. Open the Registry Editor by typing regedit in the Run dialog (Win + R).
  2. Navigate to the following path in the Registry: HKEY_CURRENT_USER\Software\DBeaver Corp\DBeaver\policy
  3. Create a new value for each setting, from the table below based on desired restrictions.
  4. Exit the Registry Editor and restart DBeaver to apply the changes.

Important: Editing the Windows Registry can significantly affect your system. Always make sure to back up the registry before making any changes. For more information on how to work with the Windows Registry, refer to the Microsoft Documentation on Registry Editing.

Registry settings
Registry key Type Value Description
policy.data.export.disabled DWORD 0, 11 disables data export, 0 enables data export.
policy.software.install.disabled DWORD 0, 11 blocks software installation and marketplace access, 0 allows it.
policy.software.update.disabled DWORD 0, 11 prevents checking for updates, and 0 enables update checks.

Did we resolve your issue?