> For the complete documentation index, see [llms.txt](https://docs.bsure.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsure.io/v1/user-guides/microsoft-licenses/price-settings.md).
# Price Settings
In this report you can choose whether to use Microsoft's list prices, or your own prices in your own currency when viewing your data.
In addition you will see how many users we bill your company every day
**Billed users**
This is the numbers of users used for billing of your subscription
**Filter alternatives**
* **Price selector:** Gives you the option to choose whether you want to see Microsoft's list prices or your own price
* **Currency selector:** Filter on and choose the currency you want to use for the report
**Table User Licenses Price**
* In this table you see an overview of all your user licenses with the list price from Microsoft, and your own price if you have added them yourself
**Table Company Licenses Price**
* In this table you will see all your company licenses with the list price from Microsoft, and your own price if you have added them yourself
Click the next page to see how to add your own prices
---
# 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://docs.bsure.io/v1/user-guides/microsoft-licenses/price-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.
