SaaS Adobe Integration - Entitiy User Subscription
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2026 12:09 AM
Hi,
I am currently performing SaaS - Adobe Integration .
The Adobe console is administered by a Parent Company and I need to Integrate/download the user Subscription specific to the Entity / Child Company only.
How can I Ensure only the Entity wise Adobe Subscriptions are integrated to the SN Instance.
Note: None of the parent company subscriptions must NOT get downloaded in the Entity SN Instance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2026 02:12 AM
I guess if you drop your query to any Adobe community, you will get your answer.
Because from Servicenow Standpoint, once we get endpoint , credential with proper permission from Adobe end - we can fetch the data.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2026 03:47 PM
It depends on whether your organisation has mutliple Adobe tenants in the Developer console. If all the Adobe user subscription data is in one tenant/entity, then there isn't a solution for your challenge. If the data you require is available is segregated from the "parent company", then you should be fine to set up the Adobe integration to pull this data only.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
This requirement has to be handled on Adobe’s side. To limit your integration to child-entity subscriptions in an Admin Console managed by a Parent Company, keep the data isolated at the Adobe product level. Since ServiceNow imports whatever the assigned endpoint and credentials allow, the filtering has to happen in the Adobe Admin Console itself:
1. Use Product Profiles: In Adobe Admin Console, have the Parent Company create and assign separate Product Profiles for the Child Company/Entity.
2. Limit Subscriptions: Assign the child entity’s licenses only to that Product Profile, with no parent company user/license assignments tied to it.
3. Set Scoped Credentials: When creating the Adobe Cloud integration profile with OAuth, limit API permissions and access token scope to that child Product Profile.
4.Run the Import Job: After validation, ServiceNow's scheduled SAM - Import Adobe User Subscriptions job will import only the users and entitlements mapped to that credential.
If this response was helpful, please consider marking it as the Accepted Solution/Helpful to help close out this thread.