# Default Correlation Config on Source

**URL:** <https://developer.sailpoint.com/discuss/t/default-correlation-config-on-source/111861>\
**Category:** SHF Discussion and Questions\
**Tags:** sailpoint-identity-security\
**Created:** [April 15, 2025, 6:13pm UTC](https://developer.sailpoint.com/discuss/t/default-correlation-config-on-source/111861 "2025-04-15T18:13:14Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![chandramohan27](https://avatars.discourse-cdn.com/v4/letter/c/51bf81/32.png) [@chandramohan27](https://developer.sailpoint.com/discuss/u/chandramohan27)\
**Post date:** [April 15, 2025, 6:13pm UTC](https://developer.sailpoint.com/discuss/t/default-correlation-config-on-source/111861/1 "2025-04-15T18:13:14Z")

</div>

Hi,

Is there an option to disable the Default Correlation Config on Source.

---

<div class="post-metadata">

**Author:** ![amankumargupta](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/amankumargupta/32/29688_2.png) [@amankumargupta](https://developer.sailpoint.com/discuss/u/amankumargupta)\
**Post date:** [April 15, 2025, 6:32pm UTC](https://developer.sailpoint.com/discuss/t/default-correlation-config-on-source/111861/2 "2025-04-15T18:32:20Z")

</div>

> [@chandramohan27](#):
>
> Is there an option to disable the Default Correlation Config on Source.

Hi As of now, you cannot fully disable the Default Correlation Config directly via the UI or API, but you can override it by defining Custom Correlation Rules When you define custom correlation rules for a source, those take precedence over the default ones. This effectively disables the default behavior.

for more understanding you can refer to this [Disable Default Correlation Rule - #5 by kenilelk1](https://developer.sailpoint.com/discuss/t/disable-default-correlation-rule/7558/5)

---

<div class="post-metadata">

**Author:** ![vishal\_kejriwal1](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/vishal_kejriwal1/32/10904_2.png) [@vishal\_kejriwal1](https://developer.sailpoint.com/discuss/u/vishal_kejriwal1)\
**Post date:** [April 15, 2025, 6:39pm UTC](https://developer.sailpoint.com/discuss/t/default-correlation-config-on-source/111861/3 "2025-04-15T18:39:39Z")

</div>

cannot be disabled , what is your usecase and issue you are facing ?

---

<div class="post-metadata">

**Author:** ![chandramohan27](https://avatars.discourse-cdn.com/v4/letter/c/51bf81/32.png) [@chandramohan27](https://developer.sailpoint.com/discuss/u/chandramohan27)\
**Post date:** [April 15, 2025, 7:01pm UTC](https://developer.sailpoint.com/discuss/t/default-correlation-config-on-source/111861/4 "2025-04-15T19:01:16Z")

</div>

@vishal_kejriwal1

I’m using a JDBC connector to pull Oracle EBS employee records. Below is the default correlation logic.

 ![image](https://global.discourse-cdn.com/sailpoint/original/3X/8/e/8e5107f272cd7bd0f5ce2cfa9a40054a5fc8b24f.png)

Now, We have few SailPoint Identities which has HR employeeNumber as Username..

Now because of this correlation logic, It get correlated to incorrect identity as PERSON\_ID is also numeric value.

---

<div class="post-metadata">

**Author:** ![vkashat](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/vkashat/32/9721_2.png) [@vkashat](https://developer.sailpoint.com/discuss/u/vkashat)\
**Post date:** [April 15, 2025, 7:41pm UTC](https://developer.sailpoint.com/discuss/t/default-correlation-config-on-source/111861/5 "2025-04-15T19:41:22Z")

</div>

Did you define any custom correlation logic like @amankumargupta suggested?

---

<div class="post-metadata">

**Author:** ![iamnithesh](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/iamnithesh/32/42445_2.png) [@iamnithesh](https://developer.sailpoint.com/discuss/u/iamnithesh)\
**Post date:** [April 15, 2025, 7:46pm UTC](https://developer.sailpoint.com/discuss/t/default-correlation-config-on-source/111861/6 "2025-04-15T19:46:47Z")

</div>

In my opinion, even if a custom correlation logic is configured that will NOT correlate any account, default correlation logic will always be used as custom config did not correlate the account.

As requirement is to NOT correlate any account, I think picking a different account attribute as Account ID might be the solution

---

<div class="post-metadata">

**Author:** ![chandramohan27](https://avatars.discourse-cdn.com/v4/letter/c/51bf81/32.png) [@chandramohan27](https://developer.sailpoint.com/discuss/u/chandramohan27)\
**Post date:** [April 16, 2025, 5:43am UTC](https://developer.sailpoint.com/discuss/t/default-correlation-config-on-source/111861/7 "2025-04-16T05:43:50Z")

</div>

I see, but for EBS Employee records, PERSON\_ID is the only unique attribute…

---

<div class="post-metadata">

**Author:** ![iamnithesh](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/iamnithesh/32/42445_2.png) [@iamnithesh](https://developer.sailpoint.com/discuss/u/iamnithesh)\
**Post date:** [April 16, 2025, 12:09pm UTC](https://developer.sailpoint.com/discuss/t/default-correlation-config-on-source/111861/8 "2025-04-16T12:09:46Z")

</div>

If there are not too many accounts correlated then you can manually uncorrelate them using new section named `accounts` under `Identity Management`

 ![image](https://global.discourse-cdn.com/sailpoint/original/3X/1/e/1e706cf80b29135c827eb8baec5dc99ed8d05dd2.png)  
 ![image](https://global.discourse-cdn.com/sailpoint/original/3X/4/9/4983f60d6036185919db920cf75f3e6de0055202.png)  
 ![image](https://global.discourse-cdn.com/sailpoint/original/3X/1/2/12937b5beeb543da753bde6b34bde065a8c3297a.png)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [June 15, 2025, 12:09pm UTC](https://developer.sailpoint.com/discuss/t/default-correlation-config-on-source/111861/9 "2025-06-15T12:09:53Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
