> For the complete documentation index, see [llms.txt](https://docs.alemba.com/asm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alemba.com/asm/asm-hermes/setup-and-configure-asm/configuring-your-system/system-administration-settings/ipk-and-workflow/incident-problem-and-known-error-ipk-management/ipk-classes.md).

# IPK classes

### Renaming an IPK class

{% hint style="info" %}

### Before you start

Ensure you are in the correct partition before applying the settings.

You must have **IPK Setup** selected in the Admin tab of your **General Access Security Role**.
{% endhint %}

1. Select ≡ > **Admin** > **System Administration**.

   The System Administration window appears.

   In the Explorer pane, expand **IPK Management**.
2. Select **IPK Classes** to open the window. The classifications are displayed, although you may find that one or more are already renamed.
3. Highlight the entry that you want to rename.
4. Type the name you want to assign for the selected IPK report grouping class.
5. Save the changes. Provide the Change Reasons if prompted to do so.


---

# 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.alemba.com/asm/asm-hermes/setup-and-configure-asm/configuring-your-system/system-administration-settings/ipk-and-workflow/incident-problem-and-known-error-ipk-management/ipk-classes.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.