Quick start
Quick answer
Start by loading identities from an authoritative source, connecting one application, aggregating its accounts, and correlating them to identities. That single loop is what everything else in SailPoint builds on.
Key takeaways
- Load identities from an authoritative source (usually HR)
- Connect one application and aggregate its accounts
- Correlate accounts to identities to build cubes
- Then layer roles, certifications and provisioning
This quick start is a fifteen-minute orientation to how SailPoint actually works, the mental model and the shortest path to a working demonstration. Master this single loop and the rest of the course slots into place, because almost everything SailPoint does is an elaboration of it.
The mental model
SailPoint is person-centric. It builds an identity for each person, links all their accounts from every system to that identity, and then governs the access those accounts represent, reviewing it, requesting it, provisioning it, and removing it as people join, move and leave.
The shortest working loop
Every deployment starts the same way. Get this loop working and you have a functioning governance base:
- 1. Configure the authoritative source (usually HR) that says who exists.
- 2. Run identity aggregation to create an identity cube for each person.
- 3. Connect a target application (Active Directory is the classic first target).
- 4. Aggregate its accounts and correlate them to the right identities.
- 5. Review the cubes, each person now shows their linked accounts and entitlements.
What to learn next
With cubes populated, the natural progression is: roles (group entitlements into business-meaningful units), lifecycle events (automate joiner/mover/leaver), and certifications (periodic access review). The rest of this course follows exactly that arc, from concepts, through the objects and flows, to real projects.
The objects you will touch first
Identity, Application/Source, Link (account), Entitlement, and Role. Everything else, policies, workflows, certifications, operates on these. Getting comfortable with this handful is the fastest way in.
Common pitfalls
- Connecting targets before the authoritative source, so there are no identities to correlate to.
- Skipping the identity refresh after aggregation.
- Trying to boil the ocean, start with one source and one target, then expand.
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
What is the first thing to configure?
- A. It links aggregated application accounts to the right identity cube so you can see who owns each account.
- B. Roles, lifecycle events and certifications build on the aggregated, correlated base.
- C. An authoritative source, usually HR, that identity aggregation reads to create identity cubes.
Show answer
C. An authoritative source, usually HR, that identity aggregation reads to create identity cubes.
An authoritative source, usually HR, that identity aggregation reads to create identity cubes.
What does correlation do in the quick start?
- A. An authoritative source, usually HR, that identity aggregation reads to create identity cubes.
- B. Roles, lifecycle events and certifications build on the aggregated, correlated base.
- C. It links aggregated application accounts to the right identity cube so you can see who owns each account.
Show answer
C. It links aggregated application accounts to the right identity cube so you can see who owns each account.
It links aggregated application accounts to the right identity cube so you can see who owns each account.
What comes after the basic loop?
- A. It links aggregated application accounts to the right identity cube so you can see who owns each account.
- B. An authoritative source, usually HR, that identity aggregation reads to create identity cubes.
- C. Roles, lifecycle events and certifications build on the aggregated, correlated base.
Show answer
C. Roles, lifecycle events and certifications build on the aggregated, correlated base.
Roles, lifecycle events and certifications build on the aggregated, correlated base.