SAM Pro modeling guidance for Alteryx Enterprise Full Creator

[meganfisher]

I’m looking for guidance and best‑practice recommendations on how to correctly model Alteryx licensing in ServiceNow SAM Pro so that Alteryx Designer installs are properly included in reconciliation and consume against our entitlements.

Background / Context

• We are invoiced by Alteryx for “Enterprise Full Creator” licenses (named‑user).
• These licenses entitle users to:
  • Alteryx Designer (desktop and/or cloud)
  • Other platform capabilities such as App Builder, Auto Insights, Plans, Copilot, automation services, etc.
• From a discovery standpoint, the only installed/discoverable component we have is Alteryx Designer (Desktop).
• The other capabilities are cloud/platform services and do not generate install evidence.

Where we’re struggling

We’re trying to ensure that:

• Alteryx Designer installs are counted in reconciliation
• Consumption aligns to what we are actually invoiced for (Enterprise Full Creator)
• We avoid incorrectly splitting cost or creating “phantom” licensable products

Specific questions we’re hoping the community can clarify

1. Entitlements vs installs

   • We have entitlements for Enterprise Full Creator, but the only normalized installs we see are for Alteryx Designer.
   • What is the recommended pattern for ensuring Designer installs consume against Enterprise Full Creator licenses without misrepresenting the license structure?

2. Publisher / Product on the software model

   • Should the licensable software model use:
     • Publisher/Product = Alteryx / Alteryx Designer (to align with normalization), or
     • Publisher/Product aligned to the commercial packaging (Enterprise Full Creator)?
   • How are others handling this when the commercial license name does not match the installable product name?

3. Compliance calculation

   • Since App Builder, Auto Insights, Designer Cloud, etc. are not installed products and provide no discovery data:
     • Is the expected/accepted approach to calculate compliance solely based on Alteryx Designer install and/or user evidence, with other capabilities treated as implicitly covered by the same license?
     • Are there any supported patterns to represent these platform capabilities without creating separate licensable models?

4. Behavior when there are no active rights

   • We’ve observed that Alteryx Designer installs do not appear in the reconciliation/compliance calculation when there are no active entitlements (rights) associated to the software model.
   • Is this expected SAM Pro behavior (i.e., installs are excluded from compliance until rights exist)?
   • If so, what is the recommended way to identify unlicensed usage during initial onboarding when entitlements have not yet been created?

What we are trying to avoid

• Splitting Enterprise Full Creator cost across multiple pseudo‑products
• Creating separate entitlements for non‑discoverable platform services
• Breaking normalization by forcing Designer installs to match a bundle name
• Over‑engineering parent/child models where only one real install exists

If anyone has modeled Alteryx (or similar Enterprise / role‑based platform licenses) successfully in SAM Pro, we would really appreciate insight into:

• Software model structure
• Entitlement setup
• Any platform nuances we should be aware of

Thanks in advance for any guidance or examples you’re willing to share.