> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/user-guides/management-dashboard/settings/currencies.md).
# Currencies
Manage currencies in the system.
The **Currencies** section allows you to configure which currencies your store supports.\
Currencies are configured both tenant-wide and independently for particular sites, so you can add the currencies you need.
## Adding a currency
To enable a new currency, follow these steps:
1. Go to **Settings** -> **Currencies** and choose **Add currency**.
2. Find the the currency to add by filtering the list of all available currencies by its ISO code or a country, and select the checkbox.
{% hint style="info" %} You can select multiple currencies. {% endhint %}
3. Confirm your choice with **Add currency**.
4. The added currency appears on the list of all supported currencies. Edit its exchange rate to the base currency for proper calculations.
{% hint style="info" %}
To learn more about how you can manage currencies in your system, see [Currency Service](/api-documentation/api-guides/configuration/currency-service.md) API guide.
{% endhint %}
---
# 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://developer.emporix.io/user-guides/management-dashboard/settings/currencies.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.
