--- title: "FAQ - General Questions" canonical: "https://helpcenter.mindproapps.com/space/sync/1991377685/FAQ%20-%20General%20Questions" format: markdown --- > ℹ️ **Summary: **Learn more about the most frequently asked questions from our clients and evaluators. ## **Install & Access** | **Question** | **Answer** | | --- | --- | | How can I learn more about installing and getting started with this app? | Please read more details here: [Getting Started](https://helpcenter.mindproapps.com/space/sync/1945436283/Getting+Started) | --- ## **IDPs connection & configuration** | **Question** | **Answer** | | --- | --- | | What are the Identity Providers compatible with Mindpro Sync? | Currently Mindpro Sync is compatible with leading Identity Providers like Okta, Entra ID (former Azure AD), Google Workspace, Microsoft 365, and OneLogin. We are working to add more options in the future. | | Are there any required permissions or configuration I need to do in my IDP to correctly map attributes in Mindpro Sync? | For Okta and OneLogin, no additional permissions need to be set.
In case you use Entra ID, it is required that the related application has at least "User.Read.All" permission set for default fields and “User.ReadWrite.All” permission in case you want to sync extension attributes.
Refer to [this link](https://mindpro.atlassian.net/wiki/spaces/sync/pages/1987870750) for more information. | | Can I have more than one IDP connected at the same time in Mindpro Sync? | Yes, please refer to this [link](https://mindpro.atlassian.net/wiki/spaces/sync/pages/2030370817) for more information. | | Is Mindpro Sync compatible with other data sources like Database, SQL, CRM, REST API, and SAP? | Mindpro Sync focuses on delivering the best data integration experience through Identity Providers only, but other options are under consideration in the future. | --- ## **Mapping, displaying & updating the data** | **Question** | **Answer** | | --- | --- | | Some IDPs have the ability to create custom attributes to be used in user profiles.
Does Mindpro Sync connect with these custom attributes? | Yes. Please check the “[Connection](https://helpcenter.mindproapps.com/space/sync/1945436305/Connection)” section to learn more about the list of attributes available for each IDP. | | Will all attributes mapped to Jira fields be displayed in the same way and for all spaces in that instance? | The app's settings allow you to choose between a global or by-space setting.
Global Configuration: All attributes mapped in the configuration will be displayed for all spaces in that instance.
Configuration by Space: The mapped attributes will only be displayed for the spaces selected in the configuration, and the attributes can be independently mapped directly in each space. | | Is it possible to select a user other than the issue’s Reporter or Assignee to sync data from the IdPs? | Yes. In the system configurations, you can select the user to display data for.
It can be the issues “Reporter”, “Assignee” or any other “User” that is informed in a single-user-picker field in jira.
You can also select the “Multiple Users” option and display the information for different users simultaneously. | | Why does Mindpro Sync use “Read-only” custom fields to map attributes from IDPs? | Mindpro Sync uses "read-only" custom fields because, when added to a screen in Jira, they don't appear to the user on the form screen when creating an issue. This ensures that users do not need to fill in duplicate information or even mistakenly fill in wrong information. | | Can the data mapped in Jira custom fields be used for other purposes, such as using it in queries, automations, filters, queues, etc.? | Yes, since these data are mapped in Jira custom fields of type "Read-Only", these attributes can be used to create queries, automations, filters, queues and wherever else you need. | | When is the synchronization done and the mapped fields updated with IdP data? | After the app configuration, the mapped fields are updated automatically in two scenarios:
- WHEN a new issue is created in Jira. - OR when an issue that already exists has its Reporter, Assignee, or the "User" field (defined in the settings) has its value updated. | | Can I specify an interval to the system to bring data from my IdP to Jira? | The app was developed to guarantee high-performance levels and not affect your instance's stability.
For this reason, it is not possible via configuration to define time intervals to update data in batch because this would impact the performance significantly. | --- ## **Automatic Approvals** | **Question** | **Answer** | | --- | --- | | How can I set approvers to my tickets automatically using Mindpro Sync? | There are two different options to set approvers for your issues:
- Using the IdP user hierarchy: if enable, the system will look to the reporter's or assignee's direct manager from the hierarchy and set this manager as the issue approver. Click [here](https://helpcenter.mindproapps.com/space/sync/1992458261) to learn more.
- Using workflow post-function: if enable, it uses a post function to set the approvers when an issue is transitioned to a certain status. Click [here](https://helpcenter.mindproapps.com/space/sync/2003402761/Setting+Custom+Approvers+via+Post+function) to learn more.
Important: Approvals in workflows can only be set for Jira Service Management space types.** ** | | Mindpro Sync sets approvers via IdP hierarchy.
But what happens if I already have automations or post-functions in my workflows that also set approvers for JSM spaces? | Mindpro Sync does not replace approvers that were already set by other apps or by automations/post-functions.
If the approver previously set in the "Approvers" field is the same Mindpro Sync is setting, nothing happens, the approver will remain there.
In case the approver previously set is different from the one Mindpro sync is informing, then the "Approvers" field will keep both approvers. | | I have other "Approvers" fields created via custom fields or by other apps.
Can I use them to set approvers with Mindpro Sync? | The app only reads the Jira Service Management's default "Approvers" field.
If you have other "Approvers" fields created by you or by other apps, the system will not read them since JSM also uses the default field to perform notifications and the approvals workflow. | | Since Mindpro Sync have two different ways to set approvers (by user hierarchy or post function), what happens if my workflow sets an approver and the "Approvers" field is already filled by the user hierarchy approval feature? Is there any compatibility issue? | In case you have the approver previously set by the Hierarchy and you move your workflow with a transition that also sets the approver (via post function), there are 2 expected behaviors:
1. **IF** the approver from the post function is the same person previously set by the Hierarchy **THEN **the system will understand this is the same person and will not do anything. The "approvers" field will keep with the same original approver.
2. **IF** the approver from the post function differs from the one previously set by the Hierarchy** THEN** the system will add this as an additional approver, and the "approvers" field will now have two approvers.
This means this post-function will never delete or replace people previously set on the "approvers" field.
HOWEVER, you can configure the system to update the approvers field during the issue creation or when switching the reporter/assignee to another user, by changing the [auto-assignment for approvals](https://helpcenter.mindproapps.com/space/sync/1992458261/Configuring+the+approver+auto-assign) feature settings. | --- ### **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)