> For the complete documentation index, see [llms.txt](https://docs.alemba.com/asm-hermes/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-hermes/setup-and-configure-asm/configuring-your-system/system-administration-settings/system-settings-menu/quick-notes.md).

# Quick Notes

### Viewing Quick Notes

{% hint style="info" %}

### Before you start

You must have **System Set Up** selected in the Admin tab of your **General Access security role**.
{% endhint %}

1. Select the Menu button, then **Admin**, then select **System Administration**. The System Administration window appears.
2. In the Explorer pane, expand **System**, then select **Quick Notes**. The Quick Notes window appears, listing the quick notes that are currently available.
3. **Active** is selected by default and displays all of the active quick notes. To display deleted ones, select the **Deleted** button.

### Adding a Quick Note

You can add a quick note that can be used when logging/actioning a call, request or task.

1. Select the Menu button, then **Admin**, then select **System Administration**. The System Administration window appears.
2. Select **Quick Notes** from the Explorer pane or the menu. The Quick Notes window appears, listing the quick notes that are currently available.
3. Select **Add** to add a new note.
4. Complete the details as follows:

<table><thead><tr><th width="154"></th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Type the name of the note, up to 80 characters. This will appear in the drop down list of available Quick Notes from within the call, request or task window</td></tr><tr><td><strong>Call/Request/Task</strong></td><td>Select the entity for which the note is being created</td></tr></tbody></table>

5\. In the lower **Quick Note** text area, type the details to be included in the note.

6\. Select **Visible in Self Service Portal** to make the quick note available to Analysts and Users logging in via the Self Service Portal.

7\. Select a **Security Profile** to restrict the Quick Note to Analysts with a specific security profile. Leaving the default “Unspecified” will make it available to all Analysts.

8\. Select to save the changes. Provide the Change Reasons if prompted to do so.

### Updating a Quick Note

You can change the details of a quick note to reflect changing needs of the organization/department.

1. Select the quick note you want to update. The details are displayed in the **Quick Note** text area.
2. Overwrite with the necessary changes.
3. Select to save the changes. Provide the Change Reasons if prompted to do so.

### Deleting a Quick Note

1. Select the quick note you want to delete. The details are displayed in the Quick Note text area.
2. Select the Delete icon.
3. Select to save the changes. Provide the Change Reasons if prompted to do so.

### Undeleting a Quick Note

1. **Active** is selected by default and displays all of the active quick notes. To display deleted ones, select the **Deleted** button.
2. Select **Undelete**. The quick note disappears from the list of deleted items.
3. Select the **Active** radio button to see it listed among the active quick notes.


---

# 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-hermes/setup-and-configure-asm/configuring-your-system/system-administration-settings/system-settings-menu/quick-notes.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.