Objects · Lesson

Objects overview

Quick answer

Almost everything in IdentityIQ is an object persisted as XML in the database: Identity (the cube), Link (an account), Application (a target), Bundle (a role), ManagedAttribute (a governed entitlement), plus Certification, Policy, TaskDefinition and Workflow. Learning these relationships is the key to the platform.

Key takeaways

Everything is an object stored as XML
Identity, Link, Application, Bundle, ManagedAttribute are core
Governance objects: Certification, Policy, WorkItem
Process objects: TaskDefinition, Workflow, Rule
Objects are exported and imported for deployment

The objects module documents the building blocks of the IdentityIQ data model, the objects every capability reads and writes. Understanding these, and how they relate, is what lets you reason precisely about how SailPoint behaves and how to customise it.

What this module covers

Each object has its own detailed page covering what it represents, its key attributes, how it is created and maintained, and how it is governed. This hub ties them together into a coherent model.

What you will find here

Identity, the person-centric cube at the centre of the model.
Role (Bundle), business-meaningful bundles of entitlements.
Application/Source, Entitlement, Managed Attribute.
Policy, Workflow, Approval, Certification, Task, Rule.

How to use it

Start with the Identity object (the centre of everything), then work outward to Role, Application/Source, Entitlement and the rest. Refer back whenever a lesson or a rule mentions an object you want to understand in depth.

Common pitfalls

Learning objects in isolation without the relationships between them.
Confusing Role and Bundle, they are the same object.
Ignoring the Identity as the hub that ties the model together.

Want to learn this properly?

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

See the course Ask a question

Check your understanding

IdentityIQ objects are stored as?
- A. ManagedAttribute. ManagedAttribute is the describable, owned entitlement object.
- B. XML in the database. Objects are persisted as XML in the relational database.
- C. Bundle. Bundle is the object type for business and IT roles.
Show answer
B. XML in the database. Objects are persisted as XML in the relational database.
XML in the database. Objects are persisted as XML in the relational database.
A role in the object model is a?
- A. ManagedAttribute. ManagedAttribute is the describable, owned entitlement object.
- B. Bundle. Bundle is the object type for business and IT roles.
- C. XML in the database. Objects are persisted as XML in the relational database.
Show answer
B. Bundle. Bundle is the object type for business and IT roles.
Bundle. Bundle is the object type for business and IT roles.
A governed entitlement with an owner is a?
- A. Bundle. Bundle is the object type for business and IT roles.
- B. ManagedAttribute. ManagedAttribute is the describable, owned entitlement object.
- C. XML in the database. Objects are persisted as XML in the relational database.
Show answer
B. ManagedAttribute. ManagedAttribute is the describable, owned entitlement object.
ManagedAttribute. ManagedAttribute is the describable, owned entitlement object.

Frequently asked questions

What does the term IdentityIQ object model refer to in SailPoint?

What is another point to note about IdentityIQ object model?

Start with the Identity object (the centre of everything), then work outward to Role, Application/Source, Entitlement and the rest.

What else is worth knowing about IdentityIQ object model?

Refer back whenever a lesson or a rule mentions an object you want to understand in depth.

What tends to go wrong with IdentityIQ object model?

Learning objects in isolation without the relationships between them. Ignoring the Identity as the hub that ties the model together.