> 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/customer-portal/configure-free-fields-per-work-type.md).

# Configure free fields per work type

The **Free fields per type of activity** section controls which custom fields appear per work type.

Use it to collect only the information you need.

{% stepper %}
{% step %}

### Open the portal

Open the portal you want to edit.
{% endstep %}

{% step %}

### Open Free fields per type of activity

Select the section in the left menu.
{% endstep %}

{% step %}

### Choose a work type

Select the work type you want to configure.
{% endstep %}

{% step %}

### Select the free fields

Choose which custom fields should appear.
{% endstep %}

{% step %}

### Save the settings

Click **Save**.
{% endstep %}
{% endstepper %}

### Good uses

* ask different details per service type
* keep the request form shorter
* make required input more relevant

### Frequently asked questions

<details>

<summary>Do free fields need to exist first?</summary>

Yes.

Create them before you assign them here.

</details>

<details>

<summary>Can different work types use different free fields?</summary>

Yes.

That is the main purpose of this section.

</details>

<details>

<summary>Can a free field be required?</summary>

Yes.

That depends on how the field is configured.

</details>

### Related topics

* [**Customer Portal**](/marketplace-packages-and-power-ups/power-ups/customer-portal.md)
* [**Configure items per work type**](/marketplace-packages-and-power-ups/power-ups/customer-portal/configure-items-per-work-type.md)
* [**Create a work order in Customer Portal**](/marketplace-packages-and-power-ups/power-ups/customer-portal/create-a-work-order-in-customer-portal.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/customer-portal/configure-free-fields-per-work-type.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.