Skip to content
IT Canvass
Objects · Lesson

Bundle

Quick answer

Bundle is the IdentityIQ object type that backs Roles, when you see "Bundle" in XML or the API, it means a role.

Key takeaways

  • What the Bundle object represents
  • Key attributes and relationships
  • How it is created and maintained
  • Where it appears in governance

Bundle is the internal object name for a Role in IdentityIQ. When you see “Bundle” in exported XML, in the API, or in a rule, it means a role. The UI says “Role”; the object model says “Bundle”. They are the same thing, and knowing this removes a common source of confusion during customisation.

Why the two names exist

IdentityIQ’s object model predates some of its UI terminology. The persisted class is Bundle, so exported XML defines roles as <Bundle> elements and rules that manipulate roles work with Bundle objects, even though everyone speaks of “roles” day to day.

What a Bundle contains

Exactly what a role contains: a type (business, IT), a set of profiles/entitlements or references to child roles, membership criteria, an owner and a description. Assigning a Bundle grants its access; removing it revokes it.

Where you meet the term

  • Exported XML, roles serialise as <Bundle> elements you version-control.
  • Rules and the API, code references the Bundle class.
  • Role mining and analysis, tooling may refer to bundles.

Practical takeaway

Treat “Bundle” and “Role” as synonyms. Everything the Role lesson covers, types, assignment, governance, applies directly; “Bundle” is simply the name you will encounter once you look under the UI into XML and code.

Common pitfalls

  • Thinking Bundle is a separate concept from Role, it is not.
  • Hand-editing Bundle XML without understanding entitlement references.
  • Confusing child-role references with direct entitlements in the XML.

Want to learn this properly?

Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.

Check your understanding

  1. What is a Bundle?

    • A. In exported XML and older APIs/rules.
    • B. They are the same object; the UI says Role, the model says Bundle.
    • C. The IdentityIQ object type that backs Roles, Bundle means Role.
    Show answer

    C. The IdentityIQ object type that backs Roles, Bundle means Role.

    The IdentityIQ object type that backs Roles, Bundle means Role.

  2. Where do you see the term Bundle?

    • A. The IdentityIQ object type that backs Roles, Bundle means Role.
    • B. In exported XML and older APIs/rules.
    • C. They are the same object; the UI says Role, the model says Bundle.
    Show answer

    B. In exported XML and older APIs/rules.

    In exported XML and older APIs/rules.

  3. Bundle vs Role?

    • A. In exported XML and older APIs/rules.
    • B. They are the same object; the UI says Role, the model says Bundle.
    • C. The IdentityIQ object type that backs Roles, Bundle means Role.
    Show answer

    B. They are the same object; the UI says Role, the model says Bundle.

    They are the same object; the UI says Role, the model says Bundle.

Frequently asked questions

What is the practical takeaway on Bundle object?

IdentityIQ’s object model predates some of its UI terminology.

What is worth remembering about Bundle object in practice?

Exactly what a role contains: a type (business, IT), a set of profiles/entitlements or references to child roles, membership criteria, an owner and a description.

What tends to go wrong with Bundle object?

Hand-editing Bundle XML without understanding entitlement references. Confusing child-role references with direct entitlements in the XML.
CallWhatsAppEnquire