---
title: "Configuring the approver auto-assign"
canonical: "https://helpcenter.mindproapps.com/space/sync/1992458261/Configuring%20the%20approver%20auto-assign"
format: markdown
---
> ℹ️ **Summary: **Learn how to configure the automatic assignment of the "Manager" field for user request approvals.

### **Auto-Assign Approvals Configuration**

 

To help support teams and agents to speed up the tickets resolution, Mindpro Sync brings a unique option to **auto-assign the tickets approver based on user hierarchy**. 


This option helps to make the ticket resolution agile and faster since the approver will be set in real time when the ticket is created.


---

### **Enable auto-assign approver based on user hierarchy**

 

On the app’s **Configuration screen**, in the “**Approval Configuration**” section, select the option “Enable auto-assign approver based on user hierarchy” and save it.


When you enable this configuration together with your other defined mapping configurations, Mindpro Sync will read in your IdP, the hierarchy information of the user who creates a request in your JSM Portal and **assign that user's manager as an approver automatically**, using the "Approvers" field.

When auto-assignment is enabled, you can also choose to keep or clean the “Approvers” field when you switch the issue to a different reporter/assignee/user. 

- **Keep (default):** If there is a previous approver (or approvers) in the “Approvers” field, and you switch the issue to a different reporter/assignee/user, the system will keep the content and add another approver to the field.
- **Clean**: If there is a previous approver (or approvers) in the “Approvers” field, and you switch the issue to a different reporter/assignee/user, the system will clean the field and add only the new approver, based on the hierarchy.

![Mindpro-1774986503643-2x.png](media://db8b20fd-0310-442f-a8e0-5e71c2aafa63)


---


### **Setting approver when the “Multiple Users” display option is enabled**


By default, the system assigns the approver based on the hierarchy of the user informed on the “Display Attributes from” section (Reporter, Assignee or Other user). 

However, if you select to display the attributes from [“Multiple Users"](https://helpcenter.mindproapps.com/space/sync/1992491009/Choosing+the+user+to+display+the+IDP+attributes#Option-to-display-data-for-multiple-users:), the system will open a dropdown next to the “Auto-assign” checkbox and will allow to select a different user to assign the approver from. 

- Example: if you are displaying the attributes from the Reporter, you can set the approver based on the Assignee’s hierarchy instead of the Reporter’s.

![Mindpro-1774986599771-2x.png](media://550edfea-95a4-4db7-814f-a847f065a777)



> ℹ️ **Keep in mind**
> ℹ️ 
> ℹ️ - In order to have the automatic assignment based on the hierarchy working properly, it is important to make sure the users in **both hierarchy levels** have the correct **emails set in both IDP** solution and **Jira**.
> ℹ️ - Additionally, the app uses the **default "Approvers" field** from Jira Service Management to **set up the auto-assignment**. So, if you create another field for "Approval" purposes, Mindpro Sync will not be able to read it, and the approvers may not be correctly set.

---

### **Need any help?**

Didn’t find what you were looking for? Raise a ticket [here](https://mindpro.atlassian.net/servicedesk/customer/portal/3) or get in touch at [support@mindproapps.com](mailto:support@mindproapps.com)