# SailPoint IIQ App Onboarding Approach: CIEM for GCP and GCP Based apps

**URL:** <https://developer.sailpoint.com/discuss/t/sailpoint-iiq-app-onboarding-approach-ciem-for-gcp-and-gcp-based-apps/217921>\
**Category:** IIQ Discussion and Questions\
**Tags:** identityiq\
**Created:** [August 3, 2026, 5:37am UTC](https://developer.sailpoint.com/discuss/t/sailpoint-iiq-app-onboarding-approach-ciem-for-gcp-and-gcp-based-apps/217921 "2026-08-03T05:37:22Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![pritishmhrn](https://avatars.discourse-cdn.com/v4/letter/p/9fc29f/32.png) [@pritishmhrn](https://developer.sailpoint.com/discuss/u/pritishmhrn)\
**Post date:** [August 3, 2026, 5:37am UTC](https://developer.sailpoint.com/discuss/t/sailpoint-iiq-app-onboarding-approach-ciem-for-gcp-and-gcp-based-apps/217921/1 "2026-08-03T05:37:22Z")

</div>

Hello All,

We are planning to onboard **GCP based apps** and **CIEM for GCP** to SailPoint IIQ 8.3P4.  
I have observed some recommending using Webservices connector while some suggesting Google Suite (G Suite) Connector - what is the ideal approach to achieve provisioning and deprovisioning taking into considering both human and non human accounts?

Thanks

---

<div class="post-metadata">

**Author:** ![neel193](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/neel193/32/34038_2.png) [@neel193](https://developer.sailpoint.com/discuss/u/neel193)\
**Post date:** [August 3, 2026, 7:49am UTC](https://developer.sailpoint.com/discuss/t/sailpoint-iiq-app-onboarding-approach-ciem-for-gcp-and-gcp-based-apps/217921/2 "2026-08-03T07:49:56Z")

</div>

@pritishmhrn AFAIK I know GoogleSuite connector is designed for Google Workspace like gmail, drive, etc..not for GCP IAM Resource Management. You need to make separate API calls to GCP to manage this which would be outside the scope of GSuite Connector. You might want to go with Webservices connector only where you can configure endpoints as per your requirement which you’ll not get it in Google Apps connector.

---

<div class="post-metadata">

**Author:** ![pritishmhrn](https://avatars.discourse-cdn.com/v4/letter/p/9fc29f/32.png) [@pritishmhrn](https://developer.sailpoint.com/discuss/u/pritishmhrn)\
**Post date:** [August 3, 2026, 8:07am UTC](https://developer.sailpoint.com/discuss/t/sailpoint-iiq-app-onboarding-approach-ciem-for-gcp-and-gcp-based-apps/217921/3 "2026-08-03T08:07:29Z")

</div>

Thank you! I will wait for a day to see if anyone else has different opinion and mark it as solution.

---

<div class="post-metadata">

**Author:** ![naveenkumar3](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/naveenkumar3/32/39339_2.png) [@naveenkumar3](https://developer.sailpoint.com/discuss/u/naveenkumar3)\
**Post date:** [August 3, 2026, 9:32am UTC](https://developer.sailpoint.com/discuss/t/sailpoint-iiq-app-onboarding-approach-ciem-for-gcp-and-gcp-based-apps/217921/4 "2026-08-03T09:32:41Z")

</div>

Use the Google Workspace (G Suite) connector.  
why not web service connector: webb Services connector has no native GCP/IAM object model — you’d be manually building schema, REST calls to Cloud Resource Manager/IAM APIs, and OAuth/service-account auth that the Google Workspace connector already ships with. It’s only justified if you deliberately choose to bypass the OOTB connector , which is not the case here.

---

<div class="post-metadata">

**Author:** ![pritishmhrn](https://avatars.discourse-cdn.com/v4/letter/p/9fc29f/32.png) [@pritishmhrn](https://developer.sailpoint.com/discuss/u/pritishmhrn)\
**Post date:** [August 3, 2026, 1:57pm UTC](https://developer.sailpoint.com/discuss/t/sailpoint-iiq-app-onboarding-approach-ciem-for-gcp-and-gcp-based-apps/217921/5 "2026-08-03T13:57:20Z")

</div>

Do you agree with @neel193 's response?

---

<div class="post-metadata">

**Author:** ![naveenkumar3](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/naveenkumar3/32/39339_2.png) [@naveenkumar3](https://developer.sailpoint.com/discuss/u/naveenkumar3)\
**Post date:** [August 3, 2026, 11:23pm UTC](https://developer.sailpoint.com/discuss/t/sailpoint-iiq-app-onboarding-approach-ciem-for-gcp-and-gcp-based-apps/217921/6 "2026-08-03T23:23:42Z")

</div>

You have posted a question in community, and we have given you our responses, It is you, who have to agree on responses. Which one is more likely a fit for your requirements.

---

<div class="post-metadata">

**Author:** ![pritishmhrn](https://avatars.discourse-cdn.com/v4/letter/p/9fc29f/32.png) [@pritishmhrn](https://developer.sailpoint.com/discuss/u/pritishmhrn)\
**Post date:** [August 4, 2026, 2:05pm UTC](https://developer.sailpoint.com/discuss/t/sailpoint-iiq-app-onboarding-approach-ciem-for-gcp-and-gcp-based-apps/217921/7 "2026-08-04T14:05:01Z")

</div>

Few observations:  
**SailPoint CIEM** is the modern cloud-native capability documented for **Identity Security Cloud (ISC)**. However, **IdentityIQ also supports GCP cloud governance through its OOTB Google Workspace Connector** , provided the applicable **IIQ Cloud Governance** or legacy **CAM** license is available.

Therefore:

- **IIQ without Cloud Governance/CAM:** Use the Google Workspace Connector for Google Workspace users, groups, and roles.
- **IIQ with Cloud Governance/CAM:** Use the same Google Workspace Connector to manage additional GCP objects, including service accounts, IAM roles, projects, folders, and resource permissions.
- **ISC:** Use the modern SailPoint CIEM capability and its associated ISC integrations.

---

<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:** [October 3, 2026, 2:05pm UTC](https://developer.sailpoint.com/discuss/t/sailpoint-iiq-app-onboarding-approach-ciem-for-gcp-and-gcp-based-apps/217921/8 "2026-10-03T14:05:38Z")

</div>

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