> For the complete documentation index, see [llms.txt](https://docs.premsoft.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premsoft.de/en/plugins/cms-elements/settings.md). # Settings You'll find the settings in the admin under **Extensions → My extensions → PremSoft CMS Elements → … → Configuration**. ## General ### Activate plugin The central toggle that switches the CMS elements on in your shop. * **On:** the elements are rendered in the storefront. * **Off:** the elements are not rendered (default after installation). **Control per sales channel:** use the **sales-channel selector** at the top of the configuration dialog to define which channel the setting applies to. * Choose a **specific sales channel** and set the toggle to control just that channel. * Choose **"All sales channels"** to set the option shop-wide. This lets you, for example, switch the elements on in a test channel first and roll them out everywhere later. ## Integrations ### Google Maps API key Only required if you use the **Google Maps (GDPR)** element. Enter your personal Google Maps API key here. Without a valid key the Google map cannot be loaded. > **How to get a key:** create a project in the [Google Cloud Console](https://console.cloud.google.com/), enable the "Maps JavaScript API" and create an API key there. For security, restrict the key to your shop domain. By the way, the **Map (OpenStreetMap)** element works **without** a key – if you don't need a Google map, that's the quicker alternative. ## Don't forget to save After every change, click **Save** in the top right so the setting takes effect. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.premsoft.de/en/plugins/cms-elements/settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.