> 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/admin/settings/service-preferences.md).
# Service preferences
Configure core service UI settings like domain/URLs, language/currency, login page, demo account, activation, and support links
This page allows you to configure your main UI settings. Access it via **Settings** → **Service preferences.**
Service preferences page
The page consists of the following sections:
* **Domain and URLs**: Set a domain to be used for your service, payment system URL, and emails to receive daily reports. For more information on customizing the domain name, see [Domain name](/docs/admin/settings/domain-name.md). For information on configuring the payment system, see [Payment gateway](/docs/admin/settings/payment-gateway.md).
* **Regional settings:** Choose the language and currency for your service. For more information, see [Regional settings](/docs/admin/settings/service-preferences/regional-settings.md).
* **Login page settings:** Configure your [login page](/docs/admin/settings/service-preferences/login-page-settings.md) settings.
* **Demo user account:** Navixy allows you to create a [demo user account](/docs/admin/settings/service-preferences/demo-user-account.md) to showcase the platform's features to your customers.
* **Device activation:** Configure device activation settings for your users.
* **Support**: Add links to your own release notes and support documentation (Navixy information is displayed by default).
---
# 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/admin/settings/service-preferences.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.
