> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infraon-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infraon-help/infinity-user-guide/change-management/add-change.md).

# Add Change

The "Change" module allows users to add change requests. A user is a technician who requests a change. A change could also arise from a ticket, a request, or a problem from the requester.

## Pre-requisites: <a href="#toc174553237" id="toc174553237"></a>

To add a change, the following must be pre-configured

* Requester - the user requesting the change
* Priority - priority of the change
* Change Manager - A Change Manager is usually a domain expert overlooking the change request.
* Change Implementer - A Change Implementer is the user responsible for implementing the change.
* Followers - users to be notified of the "change" status updates. Use the "Follow" button to follow directly.
* Tags - groupings used for the classification of changes.

## Instructions to add a Change <a href="#toc174553238" id="toc174553238"></a>

* Go to the "Change" page.
* Click on the "New Change" button.

If requesters have been added already, select the requester's name in the search option. If no requesters have been added or to add a new requester, use the "Add a New Requester" button. Follow the "Requester" module for details. You can select or add a requester from the next page too.

To add a change, follow the steps from the below table:

<table data-header-hidden><thead><tr><th width="261"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Label</strong></td><td><strong>Action</strong></td><td><strong>Description/Example</strong></td></tr><tr><td>Requester*</td><td>Add a new requester or search for an existing requester.</td><td>Requesters are usually technicians or users with the required permissions who can add a change.</td></tr><tr><td>Reported by </td><td>Use the icon to expand this section. Add the reporter's name and email address, if applicable.</td><td>Reporters are users raising the change on behalf of the requester.</td></tr><tr><td>Change Manager</td><td>Select a Change Manager from the list.</td><td>A change manager overlooks the change analysis and implementation.</td></tr><tr><td>Change Implementer  </td><td>Select the change implementer from the list.</td><td>A change implementer can be a user or a team responsible for implementing the change.</td></tr><tr><td>Impact Service</td><td>Select the Impact Service from the list.</td><td>This can be left blank. As the risk analysis progresses, the technicians can later select the impacted service.</td></tr><tr><td>Service Classification</td><td>Select the classification within the impacted service.</td><td>This is used when a specific service has multiple classifications. For example, if the impacted service is Network, the classifications can be connectivity, router issue, and so on. Leave this field blank if no classifications are defined.</td></tr><tr><td>Followers</td><td>Select a user to add them as followers.</td><td>Users who must be notified of the change request or any changes to the status of the change request can be added as followers. Use the 'Follow' option to self-follow the change request.</td></tr><tr><td>Tags</td><td>Select a tag to tag the change.</td><td>These tags must be predefined in the 'General Settings -> Tag Management module.</td></tr><tr><td>Subject </td><td>Add a subject line for the change.</td><td>The subject line can be a summary of the change. For example: Unable to connect to the network.</td></tr><tr><td>Description </td><td>Provide a brief description of the change.</td><td></td></tr><tr><td>Due By </td><td>It is the due date by which a team aims to implement the change.</td><td></td></tr><tr><td>Priority</td><td>Select the priority of the change from the list.</td><td></td></tr><tr><td>Risk</td><td>Select the risk level from the list.</td><td></td></tr><tr><td>Change Type</td><td>Select the type of Change from the list.</td><td><p>The changes can be of four types:</p><p>Standard Change</p><p>Major Change</p><p>Minor Change</p><p>*Emergency Change</p></td></tr><tr><td>Reason for Change</td><td>Specify the reason for requesting the change.</td><td></td></tr><tr><td>Add attachments </td><td>Use the action icon to add an attachment to the change.</td><td>Attachments can include emails, screenshots, etc.</td></tr><tr><td>Rollout</td><td>Specify the plan to rollout the change.</td><td>Leave this field blank if the rollout plan is not yet decided.</td></tr><tr><td>Rollback</td><td>Specify the plan to rollback the changes.</td><td>Leave this field blank if the rollback plan is not yet decided.</td></tr></tbody></table>

> \*Emergency Change is not part of this release. It will be implemented in a future release.

{% hint style="info" %}
**Note:** When the requester's name is added, Infraon displays the list of past interactions the requester has had. Click on the Change ID to view the details.&#x20;
{% endhint %}

Once all details are added, the user must click "Submit as New" - to submit the change.

### **Custom Change template creation.**

* Go to "Add change"
* Click on the select template.

The default templates and the ability to create custom templates for planning and specific changes. Ensure seamless data integration and automation tasks for increased efficiency.

### **E-mail alerts on asset hardware changes**

Automated Hardware Change Notifications! Enable in feature plan, select an asset, and edit sub-category. Configure templates for custom mail notifications, including logo, keys, and menu order adjustments.


---

# 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.infraon.io/infraon-help/infinity-user-guide/change-management/add-change.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.