IT CanvassTalk to an advisor
Objects · LessonBy , SailPoint Architect · Published · IdentityIQ 8.4 · all levels

Role

The Role object: a business-meaningful bundle of entitlements assigned to identities.

Quick answer

A Role groups entitlements into a business-meaningful unit (e.g. "Teller") so access can be granted and reviewed as one thing.

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

The Role object (stored internally as a Bundle) groups entitlements into a business-meaningful unit so access can be granted, requested, certified and revoked as one thing rather than as dozens of individual permissions. Roles are the backbone of role-based access control and the single biggest lever for making access manageable.

Types of role

  • Business roles model job functions (“Branch Teller”) and are what users and managers understand.
  • IT/technical roles bundle the technical entitlements a business role needs, often per application.

A common design nests them: a business role grants one or more IT roles, which in turn grant entitlements. This two-tier model keeps the business view clean while managing technical detail underneath.

How roles are assigned

  • Automatically, via membership criteria matching identity attributes (the ABAC-drives-RBAC pattern).
  • By request, chosen from the access catalogue and approved.
  • Manually, assigned by an administrator.

Assigning a role provisions its entitlements; removing it revokes them. That reversibility is what makes lifecycle-driven least privilege possible.

Assigned versus detected roles

An assigned role was granted deliberately. A detected role is inferred because an identity happens to hold all of a role’s entitlements, useful for role mining and for spotting access that should be formalised or removed.

Governing roles

Roles themselves need governance: an owner, a clear definition, and periodic review (role certification) to prevent them bloating over time. A well-scoped role is the minimum for a job; an over-broad role simply institutionalises over-privilege.

Common pitfalls

  • Over-broad roles that grant far more than a job needs.
  • Role explosion, so many narrow roles they are unmanageable.
  • Unowned, unreviewed roles that drift out of alignment with the business.

Practice challenge

+0 XPStreak ×0
Question 1 of 3
What does a Role bundle?

Frequently asked questions

What does the term Role object refer to in SailPoint?
The Role object (stored internally as a Bundle) groups entitlements into a business-meaningful unit so access can be granted, requested, certified and revoked as one thing rather than as dozens of individual permissions.
What is the practical takeaway on Role object?
A common design nests them: a business role grants one or more IT roles, which in turn grant entitlements.
What is worth remembering about Role object in practice?
A detected role is inferred because an identity happens to hold all of a role’s entitlements, useful for role mining and for spotting access that should be formalised or removed.
What tends to go wrong with Role object?
Over-broad roles that grant far more than a job needs. Role explosion, so many narrow roles they are unmanageable. Unowned, unreviewed roles that drift out of alignment with the business.
Want this with a live instructor and a lab tenant?
SailPoint IdentityIQ training →
Already working on SailPoint and stuck on a live ticket?Get an expert SailPoint developer on screen-share to finish your daily tasks with you. Deliver on time, protect your reputation and your job. Monthly support only, no task-wise plans.Task assigned · no idea where to startStill stuck · your job on the lineExpert joins your screenDelivered on timeExplore On Job Support