> 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/integrate/managing-integration/managing-events/configuring-event-management/viewing-event-types.md).

# Viewing Event Types

{% hint style="info" %}

### Before you start

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

1. Select menu, and then Admin. 
2. From the submenu, select Integration. 
3. The Integration Platform Settings window appears. 
4. Select the Events option on the explorer pane. 
5. Select a source from the Filter by Source list to view all the event types discovered on the selected source by a connector with event management capability.
6. If the source does not have any events defined, a pop-up message appears to this effect.
7. If ASM encounters an error connecting to the selected source (such as a connection or configuration error), an error pop-up message appears.
8. The Mapped checkbox on the Integration Events window indicates whether mappings have been defined for the corresponding event type.


---

# 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/integrate/managing-integration/managing-events/configuring-event-management/viewing-event-types.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.