> 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/itsm-solutions/asm-solutions/major-incident-management/configure-major-incident-management.md).

# Configure Major Incident Management

To setup MI Management you simply need to 

1. Create an MI template (Call Template)
2. Configure notifications (message templates), if you will not be using the defaults
3. To allow users to subscribe:
   * [ ] Configure the MI IPK Status as an Add-Me Status
   * [ ] Ensure the Add Me widget is visible on the SSP
   * [ ] Enable access to selected Self Service Portal Security Roles

## Configure notifications (message templates), if you will not be using the defaults

By default ASM has preconfigured message templates.  The message that will go out to users is **Call- Logged to User.**

<figure><img src="/files/vEnfaqy632fId5Bmj9r8" alt=""><figcaption></figcaption></figure>

You can update them for your organization's specific branding and language. &#x20;

You can create a custom Major Incident Message template and then add it to the message type mapping so that it will be used instead of the default call logged template.

{% hint style="info" %}
You may want to also configure message templates for update and closure notifications as well.
{% endhint %}

## Managing MI

Managing an MI is a centralized process.  Because users can add themselves, support need only work a single ticket, that is, the MI itself.  All related tickets will be linked as children to the MI.  When the MI is closed, support will be able to simultaneously close and notify all impacted users.

See the following for more information on managing linked tickets, converting incidents, KE and Problems to Major Incidents and Cloning to MI:

[Linking Explorer Option](/asm-hermes/use-asm/using-asm-core/managing-your-tickets-calls-and-ipk/call-details-explorer-options/linking-explorer-option.md)

[Change a Call from an Incident to a MI](/asm-hermes/use-asm/using-asm-core/managing-your-tickets-calls-and-ipk/working-with-calls/change-a-call-from-an-incident-to-a-problem-known-error-major-incident-or-service-request.md)

[Cloning Option](/asm-hermes/use-asm/using-asm-core/managing-your-tickets-calls-and-ipk/working-with-calls/cloning-option.md)

[Global Update Option](https://docs.alemba.com/asm-hermes-10.6.8/use-asm/using-asm-core/managing-your-tickets-calls-and-ipk/global-updates)


---

# 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/itsm-solutions/asm-solutions/major-incident-management/configure-major-incident-management.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.