> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/zarzadzanie-aplikacja-biznesowa/zarzadzanie-konfiguracja/konfiguracja-aplikacji-biznesowej-serwer-konfiguracji/dobre-praktyki-dokumentacji-parametrow-konfiguracyjnych.md).

# Best practices for documenting configuration parameters

| Area                                     | Rule                                                                                                                                                                                                                                                                          |                                                    |                                                                                                                                     |
| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Readable key names                       | <ul><li>Parameter names should clearly indicate their purpose and usage context.</li></ul>                                                                                                                                                                                    |                                                    |                                                                                                                                     |
| Parameter descriptions                   | <ul><li>Comments should be added to the configuration (preceded by the # sign) to explain the meaning and use of a given parameter, default values, ranges, or impact on application behavior.</li><li>The comment can also include the parameter's change history.</li></ul> |                                                    |                                                                                                                                     |
| Parameter differentiation by environment | <ul><li>Parameters can be differentiated for environments (e.g. <code>parameterName                                                                                                                                                                                           | test=testParameterValue</code> <code>parameterName | prod=prodParameterValue</code>). It is worth documenting which parameters are environment-specific and which are global. </li></ul> |
| Deployment and business parameters       | <ul><li>Deployment parameters should be separated from business parameters. Technical parameters, e.g. service addresses, should be stored in deployment configuration, while business parameters (e.g. limits, feature flags) in low-code configuration.</li></ul>           |                                                    |                                                                                                                                     |
| Editing permissions in Eximee Dashboard  | <ul><li>It should be documented whether the parameters can be edited in Eximee Dashboard and who can edit them (e.g. a group of people with the role <code>feature\_config\_edit</code>).</li></ul>                                                                           |                                                    |                                                                                                                                     |


---

# 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.eximee.com/documentation/documentation-en/zarzadzanie-aplikacja-biznesowa/zarzadzanie-konfiguracja/konfiguracja-aplikacji-biznesowej-serwer-konfiguracji/dobre-praktyki-dokumentacji-parametrow-konfiguracyjnych.md?ask=<question>&goal=<user_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.