Study guide

16.1 Default Role Models and Role Types

SailPoint Certified IdentityIQ Engineer Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: The IdentityIQ Engineer Exam

1.1 Exam Format, Official Blueprint, and Study Strategy

2 Chapter 2: Infrastructure, Installation, and Extended Attributes

2.1 IdentityIQ Infrastructure Components 2.2 Installation Steps and Procedures 2.3 Creating Extended Attributes and the Objects That Support Them

3 Chapter 3: Build, Deployment, Patching, Access, and Email

3.1 Ongoing Build and Deployment 3.2 Installing Patches and Performing Upgrades 3.3 Configuring End-User Access 3.4 Email Server Settings and Email Redirection

4 Chapter 4: Lifecycle Manager Configuration, Provisioning Policies, and Workflows

4.1 Configuring Lifecycle Manager 4.2 Identity Provisioning Policies 4.3 Configuring LCM Workflows

5 Chapter 5: Lifecycle Events, QuickLinks, Batch Requests, and Rapid Setup

5.1 Lifecycle Events and Their Workflows 5.2 QuickLinks and QuickLink Populations 5.3 Configuring and Using Batch Requests 5.4 Rapid Setup in Lifecycle Events and Identity Operations

6 Chapter 6: Certification Campaigns and Certification Rules

6.1 Configuring and Scheduling Certification Campaigns 6.2 The Purpose of Common Certification Rules

7 Chapter 7: Policies and Policy Violations

7.1 Configuring and Leveraging Policies 7.2 Responding to Policy Violations

8 Chapter 8: Reporting, Advanced Analytics, and Auditing

8.1 Executing and Leveraging Reports 8.2 Leveraging Advanced Analytics 8.3 Configuring and Using Auditing

9 Chapter 9: Rules, Rule Libraries, and the SailPoint API

9.1 The Purpose and Use of Rule Libraries 9.2 Rule Input and Output Arguments 9.3 Common SailPoint API Objects and Methods

10 Chapter 10: Workflow Development

10.1 Workflow Variables, Transitions, and Step Conditions 10.2 Workflow Steps That Generate Work Items 10.3 The Different Workflow Step Usages 10.4 Leveraging Sub-Workflows

11 Chapter 11: Email Templates, Branding, and Localization

11.1 Customizing and Using Email Templates 11.2 Branding the SailPoint User Interface 11.3 Localizing the SailPoint UI

12 Chapter 12: Application Definitions, Connector Settings, and Rapid Setup Aggregation

12.1 Configuring Application Definitions 12.2 Configuring Common Connector Settings 12.3 Configuring Rapid Setup Aggregation Settings

13 Chapter 13: Data-Loading Tasks and Application and Connector Rules

13.1 Scheduling Tasks for Data Loading and Processing 13.2 Common Application Rule Types 13.3 Common Connector Rule Types

14 Chapter 14: Debugging with log4j, Syslog, and the IdentityIQ Console

14.1 Configuring and Leveraging log4j 14.2 Configuring and Leveraging Syslog 14.3 Leveraging the IdentityIQ Console for Debugging

15 Chapter 15: Debug Pages and the Administrator Console

15.1 Leveraging the Debug Pages for Debugging 15.2 Leveraging the Administrator Console for Debugging

16 Chapter 16: Role Model and Identity Attribute Mappings

16.1 Default Role Models and Role Types 16.2 Configuring Roles and Role Options 16.3 Configuring Identity Attribute Mappings

17 Chapter 17: Data Objects, Relationships, and Group Types

17.1 Common IdentityIQ Data Objects 17.2 Relationships Between Common Data Object Models 17.3 The Difference Between Group Types

16.1 Default Role Models and Role Types

Key Takeaways Explain This Topic AI

The four default role types are Organizational (containers for navigation), Business (job functions, assigned), IT (entitlement bundles, detected), and Entitlement (legacy, not recommended).

In the two-tier model, business roles link to IT roles through Required Roles (always provisioned) and Permitted Roles (allowed on request).

Business roles are assigned by assignment rules or requests; IT roles are detected when an identity's entitlements satisfy the role's profiles.

With inheritance, only the deepest matching role in a hierarchy is assigned or detected, and organizational roles in the chain break inheritance.

Role type definitions switch capabilities on or off, such as profiles, assignment rules, manual assignment, detection, inheritance, and required and permitted lists.

Last updated: September 2026

Default Role Models and Role Types

Objective 7.1 asks you to understand default role models and types . A role (object class Bundle ) packages access. IdentityIQ's default configuration uses four role types arranged in a two-tier model .

The Four Default Role Types

Type Represents Assigned or detected? Notes

Organizational Containers that organize the role hierarchy in the Role Modeler Neither. They only provide nesting. Group roles by org structure, application, alphabet, or any scheme that helps administrators navigate

Business Job functions, titles, or responsibilities , such as AP Clerk or Treasury Analyst . The desired state of access. Assigned , automatically by assignment rules or through requests Birthright business roles are often not requestable and may be excluded from certifications

IT Sets of system entitlements on one or more applications. The actual state of access. Detected from entitlements, and can also be provisioned Group related entitlements for reuse. Too many makes them single-use, and too few causes role explosion.

Entitlement A single entitlement on one application Legacy Kept for backward compatibility with 5.x and earlier; not recommended

Custom role types can model structures that do not fit the defaults, and the default types can be reconfigured (section 16.2). Rapid Setup adds a birthright type, rapidSetupBirthright by default (section 5.4).

The Two-Tier Model

Business roles are what managers and reviewers understand. IT roles are what target systems understand. In the two-tier model , business roles link to IT roles, so a manager can approve "AP Clerk" without reading twenty group names. One IT role can serve many business roles.

Required vs. Permitted

Relationship Meaning Provisioning effect

Required Roles Access someone with the business role must have Assigning the business role provisions the required IT roles' entitlements

Permitted Roles Access the person may have, "pre-screened" but discretionary, such as VPN Nothing is provisioned until someone requests it

Required and permitted links also show missing entitlements during certifications, although certifications do not fix them. Refresh or other processes do.

Hard vs. soft permitted: a hard permitted role was requested through IdentityIQ . A soft permitted role was discovered through aggregation and correlation. When the parent business role is removed, hard permitted roles are also deprovisioned (if nothing else depends on them), and soft ones are not.

How Roles Reach Identities

Assignment (business roles): an assignment rule (Match List, Filter, Script/Rule, or Population) is evaluated when Identity Refresh runs with "Refresh assigned, detected roles and promote additional entitlements." Assignment can also come from LCM requests or batch requests.

Detection (IT roles): the same refresh option compares each IT role's profiles with the identity's entitlements. Profile filters joined by AND require all entitlements, and OR requires any. A detected role replaces its individual entitlements in the identity's entitlement view. A role can be detected more than once when different assignments target different accounts.

Loading diagram... Two-tier role model

Inheritance

Business roles: with increasingly specific criteria, such as Help Desk Level 1, then 2, then 3, an identity is assigned only the deepest matching role .

IT roles: when one set of access is a superset of another, only the deepest role is detected, and only if all entitlements of the chain are present. For example, Developer inherits Engineering.

Limits: an organizational role placed in the chain breaks inheritance . Inheritance works only between roles of the same type. An IT role cannot be inherited directly by a business or container role.

Designing a Role Model: Practical Guidance

Start with business roles people recognize. Use job codes, departments, and titles from HR. If reviewers cannot explain a role name, it will be rubber-stamped in certifications.

Build IT roles around reuse. An IT role should bundle entitlements that several business roles share. SailPoint warns about both extremes: over-grouped IT roles are single-use, and under-grouped ones cause role proliferation .

Use organizational roles only for navigation. They do nothing at run time, and placing them inside an inheritance chain breaks inheritance.

Keep birthright separate. Birthright business roles, such as "All Employees," are usually assigned by rule, not requestable, and often excluded from certifications.

Use required roles for provisioning and permitted roles for pre-approved options. This keeps requests fast and approvals meaningful.

Let detection reveal gaps. Detected IT roles that are not covered by any assigned business role show access that came from outside the model, which is a good target for certification.

What a Role Type Controls

A role type definition sets what roles of that type can do. The options include disallow inheritance , no automatic detection with profiles (or no detection unless assigned), no entitlement profiles , no automatic assignment with rule , no manual assignment , no permitted or required roles list , disallow appearing on permitted or required lists , and disallow granting IdentityIQ user rights . This is why, for example, the Role Editor shows no Assignment Rule panel for an IT role and no entitlement panel for an organizational role.