> 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-items-per-work-type.md).

# Configure items per work type

The **Items per type of activity** section controls which items belong to each work type.

Use it to simplify request creation for customers.

{% stepper %}
{% step %}

### Open the portal

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

{% step %}

### Open Items 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 items

Choose which items should be available for that work type.
{% endstep %}

{% step %}

### Save the settings

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

### Why this helps

* keeps the request form shorter
* prevents irrelevant item choices
* guides customers toward the right selection

### Frequently asked questions

<details>

<summary>What happens if I set no items?</summary>

That depends on your setup.

In many cases, customers can see a broader item list.

</details>

<details>

<summary>Can one item belong to multiple work types?</summary>

Yes.

You can reuse items across work types.

</details>

<details>

<summary>Do I need work types first?</summary>

Yes.

You configure items per existing work type.

</details>

### Related topics

* [**Customer Portal**](/marketplace-packages-and-power-ups/power-ups/customer-portal.md)
* [**Configure user settings and permissions**](/marketplace-packages-and-power-ups/power-ups/customer-portal/configure-user-settings-and-permissions.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-items-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.