# Stakeholder Roles

## System Stakeholder Roles

ASM contains special stakeholder roles. You should not modify or alter these roles. 

### The Email Recipients role

One such role is "Email Recipients".  Users CC'd via email can automatically be added as stakeholders to the ticket (see [Outgoing Email Server Settings](https://docs.alemba.com/asm-hermes-10.6.8/setup-and-configure-asm/setting-up-your-system/setup-email/setting-up-incoming-and-outgoing-email) for more information).  This allows ASM to include these special "stakeholders" in email responses.  You can also [add stakeholders](https://docs.alemba.com/asm-hermes-10.6.8/use-asm/using-asm-core/managing-your-tickets-calls-and-ipk/call-details-explorer-options#workflow-group) with this role ad-hoc to have the listed individuals or groups receive email updates.

### The Follower role

Available after 10.6.8.15097

This role allows Users to view Calls, Requests, and Approvals where they are assigned the Follower role in the Self Service Portal (SSP).  

{% hint style="info" %}
The Self Service Portal Role>Options>**Manage Stakeholder Calls** (to follow calls) and **Manage Stakeholder Requests** (to follow requests) options must be enabled

<img src="/files/WbjSXjC0y0UCDBqKJQoe" alt="" data-size="original">

<img src="/files/zKE7m8UbzU6J4NWRoxPg" alt="" data-size="original">
{% endhint %}

Users with this role can:

* Search for and view Incidents, Requests, or Approvals where they are assigned the Follower role.
* Access Call details, including a read-only Call history and conversation history.
* Followers can also Chase the call on behalf of the assigned user to the call, with appropriate permission are applied (they must also have[ call chase](https://docs.alemba.com/asm-hermes-10.6.8/setup-and-configure-asm/configuring-your-system/system-administration-settings/self-service-portal/self-service-portal-settings-partitioned) enabled).
* Add or remove themselves from following a Call. This option applies to Calls, Requests, and Approvals.

### The Stakeholder role

The other System Stakeholder role is "Stakeholder". Alemba recommends you do not change this role as it is a the System Default.  If you rename it, identifying it at a later date will require a DB query.

### Creating Stakeholder Roles

{% hint style="info" %}

### Before you start

As some parameters are read from the database at application start-up, we recommend that there are no Analysts logged on when you make changes to system settings.

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** in order to configure any IPK administration settings.
{% endhint %}

1. Select ≡ > **Admin** > **System Administration**.  The System Administration window appears.
2. In the Explorer pane, expand **IPK Management**.
3. Select **Call Stakeholder Roles** to open the window. A list of existing stakeholder roles appears.
4. Select the Plus icon. A row is inserted in the browse table.
5. Type a name for the stakeholder type into the Name field.
6. Save the changes.&#x20;
7. Provide the Change Reasons if prompted to do so.

### Renaming Stakeholders

1. Select ≡ > **Admin** > **System Administration**. The System Administration window appears.&#x20;
2. In the Explorer pane, expand **IPK Management**.
3. Select **Call Stakeholder Roles** to open the window. A list of existing stakeholder roles appears.
4. To rename an existing stakeholder type, select it and type a new name over the existing one.
5. Save the changes.&#x20;
6. Provide the Change Reasons if prompted to do so.

### Deleting Stakeholder Roles

{% hint style="info" %}
You cannot delete system values
{% endhint %}

1. Select ≡ > **Admin** > **System Administration**. The System Administration window appears.&#x20;
2. In the Explorer pane, expand **IPK Management**.
3. Select **Call Stakeholder Roles** to open the window. A list of existing stakeholder roles appears.
4. Select the stakeholder role you want to delete. Select the delete (Trash can) Icon . If you attempt to delete the system default, you will receive a warning message.
5. Save the changes.&#x20;
6. Provide the Change Reasons if prompted to do so.


---

# Agent Instructions: 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:

```
GET https://docs.alemba.com/asm-hermes/setup-and-configure-asm/configuring-your-system/system-administration-settings/ipk-and-workflow/incident-problem-and-known-error-ipk-management/call-stakeholder-roles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.