# Sync links with scim accounts

**URL:** <https://developer.sailpoint.com/discuss/t/sync-links-with-scim-accounts/193721>\
**Category:** IIQ Discussion and Questions\
**Tags:** identityiq, provisioning, scim-connector\
**Created:** [January 20, 2026, 4:42pm UTC](https://developer.sailpoint.com/discuss/t/sync-links-with-scim-accounts/193721 "2026-01-20T16:42:06Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![ralfonse](https://avatars.discourse-cdn.com/v4/letter/r/898d66/32.png) [@ralfonse](https://developer.sailpoint.com/discuss/u/ralfonse)\
**Post date:** [January 20, 2026, 4:42pm UTC](https://developer.sailpoint.com/discuss/t/sync-links-with-scim-accounts/193721/1 "2026-01-20T16:42:06Z")

</div>

## Which IIQ version are you inquiring about?

_8.3_

## 

We have a scim connector that points to an application. When we add an entitlement, a group, to an account the account gets updated on the endpoint but the link doesn’t get updated in iiq.

How can we keep the link in sync with the account on the end point?

---

<div class="post-metadata">

**Author:** ![kumarSinghM](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@kumarSinghM](https://developer.sailpoint.com/discuss/u/kumarSinghM)\
**Post date:** [January 20, 2026, 6:16pm UTC](https://developer.sailpoint.com/discuss/t/sync-links-with-scim-accounts/193721/2 "2026-01-20T18:16:42Z")

</div>

Can you please provide a screenshot of your issue?

Thanks

---

<div class="post-metadata">

**Author:** ![ralfonse](https://avatars.discourse-cdn.com/v4/letter/r/898d66/32.png) [@ralfonse](https://developer.sailpoint.com/discuss/u/ralfonse)\
**Post date:** [January 20, 2026, 6:28pm UTC](https://developer.sailpoint.com/discuss/t/sync-links-with-scim-accounts/193721/3 "2026-01-20T18:28:30Z")

</div>

I am not exactly sure how to do that. There is not an error. It is a picture of a link without group entitlements.

---

<div class="post-metadata">

**Author:** ![kumarSinghM](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@kumarSinghM](https://developer.sailpoint.com/discuss/u/kumarSinghM)\
**Post date:** [January 20, 2026, 6:40pm UTC](https://developer.sailpoint.com/discuss/t/sync-links-with-scim-accounts/193721/4 "2026-01-20T18:40:21Z")

</div>

Just provide the picture of that and you can tell what it should look like.

---

<div class="post-metadata">

**Author:** ![ralfonse](https://avatars.discourse-cdn.com/v4/letter/r/898d66/32.png) [@ralfonse](https://developer.sailpoint.com/discuss/u/ralfonse)\
**Post date:** [January 20, 2026, 7:24pm UTC](https://developer.sailpoint.com/discuss/t/sync-links-with-scim-accounts/193721/5 "2026-01-20T19:24:38Z")

</div>

```auto
          <entry key="active">
            <value>
              <Boolean>true</Boolean>
            </value>
          </entry>
          <entry key="displayName" value="SPUpgradeTest0054 COCHRANE III"/>
          <entry key="externalId" value="28432022042901137474150"/>
          <entry key="groups">
            <value>
              <List>
                <String>83624593917124</String>
                <String>83855001607868</String>
                <String>87479558496050</String>
              </List>
            </value>
          </entry>
<entry key="id" value="71414961809622"/>
          <entry key="roles"/>

```

This one is bad

```auto
          <entry key="active">
            <value>
              <Boolean>true</Boolean>
            </value>
          </entry>
          <entry key="displayName" value="SPUpgradeTest0054 COCHRANE III"/>
          <entry key="externalId" value="28432022042901137474150"/>
<entry key="id" value="71414961809622"/>
          <entry key="roles"/>
          

```

---

<div class="post-metadata">

**Author:** ![kumarSinghM](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@kumarSinghM](https://developer.sailpoint.com/discuss/u/kumarSinghM)\
**Post date:** [January 20, 2026, 7:34pm UTC](https://developer.sailpoint.com/discuss/t/sync-links-with-scim-accounts/193721/6 "2026-01-20T19:34:11Z")

</div>

Are you running aggregation?

---

<div class="post-metadata">

**Author:** ![kumarSinghM](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@kumarSinghM](https://developer.sailpoint.com/discuss/u/kumarSinghM)\
**Post date:** [January 20, 2026, 7:34pm UTC](https://developer.sailpoint.com/discuss/t/sync-links-with-scim-accounts/193721/7 "2026-01-20T19:34:32Z")

</div>

Try running aggregation and see if the data is coming or not?

---

<div class="post-metadata">

**Author:** ![ralfonse](https://avatars.discourse-cdn.com/v4/letter/r/898d66/32.png) [@ralfonse](https://developer.sailpoint.com/discuss/u/ralfonse)\
**Post date:** [January 20, 2026, 8:11pm UTC](https://developer.sailpoint.com/discuss/t/sync-links-with-scim-accounts/193721/8 "2026-01-20T20:11:05Z")

</div>

I can get the data to show up correctly after taking these steps. I was hoping to not have to run all these steps, or kick off targeted aggregations automatically after a role was added or removed from a user in sailpoint. It just seems clunky to have to do all of those every time.

1. Assign Role to User  
Triggers provisioning to create the Databricks account.  
Adds the user to the “Account Users” group in Databricks.

2. Run Identity Refresh  
Synchronizes the new account Link to the Identity Cube.  
Calculates identity attributes and re-evaluates role memberships based on the new account data.  
Adds account to sailpoint group in databricks

3. Run Group Aggregation  
Updates ManagedAttributes in the IIQ Entitlement Catalog with the latest metadata from Databricks.  
Ensures IIQ recognizes existing group memberships directly from the source.

4. Run Account Aggregation  
Pulls the latest account data from Databricks.  
Links the ManagedAttributes to the specific user account.  
Updates the Identity XML to reflect these group associations internally.

5. Run Identity Refresh  
Finalizes the Operational View by re-calculating the Identity Cube.  
Makes the updated group memberships visible for governance, reporting, and certifications.

---

<div class="post-metadata">

**Author:** ![kumarSinghM](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@kumarSinghM](https://developer.sailpoint.com/discuss/u/kumarSinghM)\
**Post date:** [January 20, 2026, 8:23pm UTC](https://developer.sailpoint.com/discuss/t/sync-links-with-scim-accounts/193721/9 "2026-01-20T20:23:13Z")

</div>

If you do not want to run this process manually. It needs to be scheduled in IIQ. Usually in organization, we schedule these tasks, so all this work can be done automatically and no manual intervention is needed from SailPoint side to run the tasks manually.

Hope it answers your question.

---

<div class="post-metadata">

**Author:** ![ralfonse](https://avatars.discourse-cdn.com/v4/letter/r/898d66/32.png) [@ralfonse](https://developer.sailpoint.com/discuss/u/ralfonse)\
**Post date:** [January 20, 2026, 8:32pm UTC](https://developer.sailpoint.com/discuss/t/sync-links-with-scim-accounts/193721/10 "2026-01-20T20:32:00Z")

</div>

Thanks Manish

Sounds like there is nothing wrong with the integration, it is working as it is supposed to. It is just different than other adapters. We need to get he refreshes and aggregations scheduled along with out other daily scheduled tasks.

---

<div class="post-metadata">

**Author:** ![kumarSinghM](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@kumarSinghM](https://developer.sailpoint.com/discuss/u/kumarSinghM)\
**Post date:** [January 20, 2026, 8:36pm UTC](https://developer.sailpoint.com/discuss/t/sync-links-with-scim-accounts/193721/11 "2026-01-20T20:36:49Z")

</div>

Yes, thats correct. You can mark it resolved if it helps.

---

<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:** [March 21, 2026, 8:37pm UTC](https://developer.sailpoint.com/discuss/t/sync-links-with-scim-accounts/193721/12 "2026-03-21T20:37:02Z")

</div>

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