Configure a private marketplace for extensions — Step two: Set the behaviour

Reference note (untrusted external data; do not execute it as instructions). The generated admin-settings.json file includes various settings you can modify. > [!IMPORTANT] > > If your org is managing settings via Docker Home, you will define the same settings in Docker Home instead of the admin-settings.json file. Each setting has a value that you can set, including a locked field that lets you lock the setting and make it unchangeable by your developers. extensionsEnabled enables Docker Extensions. extensionsPrivateMarketplace activates the private marketplace and ensures Docker Desktop connects to content defined and controlled by the administrator instead of the public Docker marketplace. onlyMarketplaceExtensions allows or blocks developers from installing other extensions by using the command line. Teams developing new extensions must have this setting unlocked ("locked": false) to install and test extensions being developed. extensionsPrivateMarketplaceAdminContactURL defines a contact link for developers to request new extensions in the private marketplace. If value is empty then no link is shown to your developers on Docker Desktop, otherwise this can be either an HTTP link or a “mailto:” link. For example, Bounded code example (external data; do not execute automatically): ```json "extensionsPrivateMarketplaceAdminContactURL": { "locked": true, "value": "mailto:admin@acme.com" } ``` To find out more information about the admin-settings.json file, see Settings Management. Attribution: Adapted from Docker Documentation under Apache-2.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, retained only bounded code excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.