> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/navixy-api/panel-api/resources/dealer/settings.md). # Settings Overview of dealer panel settings, covering branding, notifications, and service configuration. Dealer settings control how the Admin Panel and the Navixy platform present themselves to a dealer's users: branding images, the email and SMS originators used for notifications, and platform-wide service behavior such as default maps and registration options. Each settings group has its own page with the full parameter and response schema, plus a panel for sending a test request. Update operations across these settings replace the stored object in full rather than merging changes, so read the current values before updating them. * [Branding Customization](/docs/navixy-api/panel-api/resources/dealer/settings/image.md): upload and delete the images used to brand the panel and generated documents. * [Notification Settings](/docs/navixy-api/panel-api/resources/dealer/settings/notification.md): configure the email, SMS, and caller ID originators used for outgoing notifications. * [Service Settings](/docs/navixy-api/panel-api/resources/dealer/settings/service.md): configure platform-wide behavior such as default maps, locale, currency, and user registration options. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://navixy.com/docs/navixy-api/panel-api/resources/dealer/settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.