> 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/additional-config.md). # Additional Config Everything in this section has a working default. You can install Limio for Salesforce, configure your offers, and go live without touching any of it. Come back here when a specific requirement forces the change — a custom address field your fulfilment needs, invoice as a payment method, an extra column on the subscriptions table.

Area	Change it when
Subscription Actions	Agents should see a different set of actions than the defaults allow
Addresses	You need custom address fields, postcode validation, or US NCOA handling
Payment Methods	You take invoice payments, or need to capture an additional payment mid-flow
Custom Fields	Orders must carry data beyond Limio's standard fields
Subscriptions Table	Agents need different columns on the subscriptions list
Apex Classes	You are building custom Apex against Limio's global classes

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.limio.com/salesforce/setting-up/additional-config.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.