> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/salesforce/setting-up/add-ons-config/add-ons-label.md).
# Labels
**LFS version compatibility**: available with LFS v12.20 or later
The ability to customise even the tiniest details, such as a button label or a notification message, is incredibly valuable for businesses. It allows them to tailor every aspect of their system and reflect their vision much better.
Take the 'Add-Ons' entity, for example, which is a part of the acquisition order flow.
While 'Add-Ons' is the default label, it might not accurately represent the function of this entity for every business. Some businesses may prefer to call it 'Credit Memos', 'Additional Charges', or something completely different.
This article will show you how you can customise the label to perfectly fit your business needs.
1. In the Limio Acquisition Journey, locate the Selected Offers screen.
2. Click on the Limio Selected Offers Table and find an \`Add-On label\` input property.
3. Enter the custom label and Save your changes.
The custom label is going to be reflected in the highlighted areas on the screen:
---
# 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.limio.com/salesforce/setting-up/add-ons-config/add-ons-label.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)