> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/f-gases-forms-koudsmart/configure-the-location-column.md).

# Configure the location column

The location column controls how installations appear in the KoudSmart report output.

A clear location format makes the report easier to review.

### What this setting does

This setting builds one clear location line in your report.

You choose which details appear in that line.

You can combine object details, customer details, and address details.

### Good location choices

Use details that help users recognize the installation quickly.

Good choices often include the object location, customer name, and address.

Keep the result short enough to scan easily.

{% stepper %}
{% step %}

### Open the report settings

Go to the KoudSmart reporting area.
{% endstep %}

{% step %}

### Review the location options

Select the details that should build the location line.
{% endstep %}

{% step %}

### Arrange the order

Put the most useful detail first.

Add plain text if that makes the result clearer.
{% endstep %}

{% step %}

### Save the selection

Save the configuration before you generate the report.
{% endstep %}

{% step %}

### Test the result

Generate a report and check whether the location format is clear enough.
{% endstep %}
{% endstepper %}

### Frequently asked questions

<details>

<summary>Why does the location column matter?</summary>

It helps identify installations in the report quickly.

</details>

<details>

<summary>Can I use different types of details together?</summary>

Yes.

You can combine object, customer, and address details in one location line.

</details>

<details>

<summary>Should I include too many details?</summary>

Usually no.

Keep the output readable.

</details>

<details>

<summary>Can I change the order later?</summary>

Yes.

You can adjust the order whenever needed.

</details>

<details>

<summary>Can I improve the format later?</summary>

Yes.

Review it before final reporting.

</details>

<details>

<summary>Does this change older reports?</summary>

No.

It changes reports you generate after the update.

</details>

### Related topics

* [**Generate KoudSmart reports**](/marketplace-packages-and-power-ups/power-ups/f-gases-forms-koudsmart/generate-koudsmart-reports.md)
* [**Object Management**](/marketplace-packages-and-power-ups/power-ups/object-management.md)
* [**Understand refrigerant registration**](/marketplace-packages-and-power-ups/power-ups/f-gases-forms-koudsmart/understand-refrigerant-registration.md)


---

# 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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/f-gases-forms-koudsmart/configure-the-location-column.md?ask=<question>&goal=<endgoal>
```

`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.