We’re integrating Docusign using the IDN connector DocuSign eSignature. Indeed, only entitlement type “group” are aggregated. We’re unbale to aggregate “permission_profile” type (neither by accounts aggregation nor by entitlement aggregation).
However, we’ve created a source schemas “permission_profile” :
Hi @timahm, there is already DocuSign eSignature (SaaS) connector available in IdentityNow. You don’t need to configure Web Services source for this one.
The OOTB DocuSign eSignature connector already has permissionProfileId and permissionProfileName as an account schema attribute and this can be also managed as entitlement.
Create account supports this attribute as per the DocuSign API, permissionProfileId attribute can be set as “Entitlement” and then assigning that while creating account should also work. Alternately, it can be added in the “Create Account” as well. For example, it could be like creating roles with those entitlements and add criteria to them; so it can be assign when user is in Active LCS. There should not be any issue.