Bundle
The Bundle object: IdentityIQ's internal name for a Role.
Bundle is the IdentityIQ object type that backs Roles, when you see "Bundle" in XML or the API, it means a role.
- 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
Bundleclass. - 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.