I went through the Coupa SaaS Connector documentation - Integrating SailPoint with Coupa SaaS . Various coupa entitlements like roles, content groups, account groups, approval groups and user groups are supported for aggregation and provisioning. But how do we manage Coupa user license updates? Coup…

Hi @imagavis I haven’t worked on Coupa connector, but in generic terms, these kind of scenarios where when a specific profile is requested, a set of other profiles to be revoked can be achieved using workflows. Here is what I would suggest for workflow: Mark the license attributes in account sch…

Thanks @uday_kilambi for the response. The problem with Coupa SaaS connector is that I won’t be able to update the account schema attribute and mark it as Entitlement. Refer the snip below. How can we tackle the requirement in this case? How can I trigger a update to Coupa account attributes? [i…

Hi @imagavis , Unable to define it as an entitlement will be a blocker as you cannot make it requestable as an entitlement or access profile. But, I don’t think that is the case here. The type of attribute is defined as boolean and hence you won’t be able to define it as entitlement, but you chang…

Hi @imagavis , You do not need to define an entitlement type, it can be of type string only. When you run an aggregation, all the unique values of the attribute, in this case TRUE and FALSE will be promotes as an entitlement by the account aggregation task. Regards, Uday Kilambi

Hi @imagavis , One way to do that it’s to use the SaaS Connectors Customizer Commands . Maybe using the Account List you will be able to intercept the Account Aggregation and change the values that you are reading from Coupa. Regards,

Thanks @uday_kilambi for the suggestion. I tried the solution suggested and unfortunately it didn’t work.

@imagavis Were you not able to change the type to String? Or even after changing the type to string, you were unable to mark it as an entitlement? Which was the case here.

@uday_kilambiCTS I was able to change the type to string and marked the specific attribute as entitlement but post account and group aggregation the values for the attribute didn’t get imported as an entitlement. Please let me know if you need further details

@imagavis , That is strange, if the attribute is marked as an entitlement, it should be promoted as an entitlement after account aggregation. You can try executing unoptimized aggregation. If it still doesn’t work, can you post a screenshot of the schema configuration of this attribute and any use…

Coupa Saas Connector - Account Update Usecase Support

Identity Security Cloud (ISC) ISC Discussion and Questions

imagavis (Sivagami Annamalai) June 25, 2024, 5:02am 5

Thanks @uday_kilambi for the suggestion! Marking the attribute as entitlement is showing the below prompt. And I don’t see a flexibility to define a new entitlement type in the Coupa SaaS connector. How do we proceed here?

Topic		Replies	Views
Best Practice for Assigning Coupa Boolean Licenses via Roles? (Not Entitlements) ISC Discussion and Questions workflows , identity-security-cloud , connectors	6	37	April 6, 2026
Get Access workflow couldn't get user role for Coupa attribute update ISC Discussion and Questions workflows , identity-security-cloud , provisioning	5	59	May 1, 2026
Coupa Provisioning error : attribute is not sync across Coupa Source ISC Discussion and Questions transforms , apis , identity-security-cloud , provisioning	14	424	September 21, 2024
Coupa Connector Entitlement Aggregation Issue ISC Discussion and Questions identity-security-cloud , connectors	3	97	March 13, 2025
Problems Reading Roles in Coupa using the SaaS Connector - Permission/Scope Issues ISC Discussion and Questions saas-connector , aggregation , identity-security-cloud , entitlements	3	23	April 21, 2026

Coupa Saas Connector - Account Update Usecase Support

Related topics