# Dynamics Integration Settings
### **Authorization Information**
You can view details about the **integration user,** the Dynamics user who connected the app, on the **Sync Settings** tab of your configuration. This section displays:
* **Integration User:** The email address of the Dynamics user who connected the integration
* **Connection Date:** The date the integration was initially connected
* **Authorization Date:** The date the integration was authorized to access Dynamics
* **User Dynamics Permissions:** The user’s Dynamics permission levels
By clicking into "See Permissions" you can view the integration user's user permissions.
### **General Settings**
In this section you can configure your integration settings for team member assignments, auto syncing, and primary sync objects.
**Integration Assignment**
You can choose which team members this integration applies to. In this section, you can assign the integration to the **full team** or to a specific **subteam** via the dropdown menu, depending on how you want leads to sync into Dynamics. [Read more on Integration hierarchies here](/introduction/integrations/microsoft-dynamics-integration/integration-types-hierarchy.md).
***
#### **Auto Sync**
This toggle controls how Popl leads flow into Dynamics. You can choose between **automatic syncing** or **manual lead selection**, depending on how much control your team needs.
**Auto Sync ON - Instant Lead Syncing (Recommended)**
When Auto Sync is enabled, every new lead captured by any team member is immediately pushed to Dynamics.
* No manual data entry
* No lead selection required
* Fast, fully automated workflow for maximum efficiency
**Auto Sync OFF - Manual Lead Selection**
When Auto Sync is turned off, leads are not automatically sent to Dynamics. Instead, admins or members choose which leads to sync. This option provides more control for teams that want to review or qualify leads first.
**Admin Controls**
* Can sync any team member’s leads at any time.
**Member Controls**
* Can sync only their own leads.
* Admins can disable member syncing if needed.
***
#### **Primary Object Sync**
Select from the dropdown menu whether you want to sync leads or contacts to Dynamics.
**Primary Object - Leads**
When syncing Popl leads to Dynamics as **Lead** records, the integration first performs a **lookup** to determine whether the lead already exists in your Dynamics org. This lookup uses the lead’s **email address** and **phone number** as the primary identifiers to match against existing Dynamics records.
Based on the results of this lookup, the integration will follow **one of three paths**:
1. **No Lead Found → Create New Lead**
If the lookup does not find an existing Lead that matches the Popl lead’s email or phone number, the integration will create a **new Lead record** in Dynamics. Lead ownership and any field mappings you’ve configured will be applied automatically according to your Dynamics Integration settings.
2. **No Lead Found, but a Contact Exists → Update Existing Contact (See Advanced Settings)**
With **update existing Contacts is toggled on** in Advanced Settings (see below), if no Lead is found, the integration will then check for an existing **Contact** with the same email or phone number.If a matching Contact is found, the integration will **update the existing Contact record** instead of creating a new Lead.
3. **Existing Lead Found → Update Existing Lead**
If a Lead is found using the Popl lead’s email or phone number, the integration will **update the existing Lead**.
Your update behavior is determined by the mapping settings you selected: **Overwrite, Complete if missing, or Append.**
***
### Advanced Settings
In the Advanced Settings section, you can choose your syncing logic and configure how notes are mapped to Dynamics. To access these options, click **Show**.
Once Advanced Settings are revealed, you can toggle each option on or off as needed.
**Sync Notes**
Have this setting toggled on to sync Popl notes to Microsoft Dynamics.
**Update Contact Logic**
Toggling this **on** will apply the custom mappings that have been set under the Contacts section to a Contact, if the Contact already exists.
*For example, if your primary sync object is Leads, but the synced lead **already exists as a contact,** we will apply the contact mappings.*
**Search For existing Accounts by Website**
In addition to search for matching Accounts via the lead email domain and company, website will be used too.
***
#### Save your Settings
Once you have configured your integration settings, be sure to save your changes. You can do this by clicking **Save** in the top-right corner of the integration configuration page.
By fine-tuning these integration settings, you can ensure that Popl and Dynamics work together seamlessly, moving your contacts where they need to go, keeping your data clean, and helping your team stay fast and efficient.
***
#### Need Help?
Contact Popl Support – our team is available to assist at .
\
With 🤍 from Popl.
---
# 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.popl.co/introduction/integrations/microsoft-dynamics-integration/dynamics-integration-settings.md?ask=
```
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.
