Study guide
5.2 QuickLinks and QuickLink Populations
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
5.2 QuickLinks and QuickLink Populations
Key Takeaways Explain This Topic AI
Three objects work together: QuickLink defines the link, DynamicScope defines the population, and QuickLinkOptions connects them.
QuickLinks cannot be created in the UI; they are XML objects, and populations are managed on Global Settings > QuickLink Populations.
The default population is Everyone; Lifecycle Manager adds Help Desk, Manager, and Self Service.
Membership can be None (listed identities only), All, Match List, Filter, Script, Rule, or Population, with explicit inclusions and exclusions.
"Who can members request for?" and "What can members request/remove?" limit LCM request authority for each population.
Last updated: September 2026
QuickLinks and QuickLink Populations
Objective 2.5 asks you to create and manage QuickLinks and QuickLink populations . QuickLinks are how users start work in IdentityIQ. They appear as cards on the Home page , which users can add or remove, and as entries in the QuickLink menu available on every page. Examples are Request Access , Manage Accounts , Create Identity , Access Reviews , Approvals , and Work Items .
The Three Objects Behind a QuickLink
- Object Role
- QuickLink Defines the link itself: its name, category in the menu, and the action it performs
DynamicScope Defines a population of users who may see and use links, based on capabilities, rights (including those inherited from workgroups), populations, or identity attributes
QuickLinkOptions A container that references one DynamicScope and one QuickLink, plus options such as allowSelf , to make the link available to that population
Key facts from the documentation:
You cannot add QuickLinks inside IdentityIQ. They are defined when IdentityIQ is deployed, usually by importing QuickLink XML. On the population's QuickLinks tab, you enable existing links for that population.
When you create a population on Global Settings > QuickLink Populations and enable links for it, IdentityIQ creates the QuickLinkOptions objects.
The DynamicScope decides who can see and run the link. It does not define the identities the link acts on after it is clicked. That is the population's request-authority setting.
Only System Administrators can see a QuickLink that has no population.
A top-level QuickLink is treated as a non-LCM action that does not operate on a target identity, so no user-selection options are shown.
Default Populations
Everyone exists by default. It is a DynamicScope with allowAll="true" . Access Reviews, Approvals, Signoffs, Work Items, and Policy Violations are linked to it by default.
With Lifecycle Manager , you also get Help Desk , Manager , and Self Service .
- Configuring a Population
- Membership
- Membership rule Meaning
- None Only identities in the Included Identities list
- All Every identity
Match List Identities matching identity attributes, application attributes, or application permissions. Is Null matches users on the chosen application whose attribute or permission is null.
- Filter A custom database query
- Script A custom script
- Rule An existing rule
- Population An existing population saved from Advanced Analytics
Included Identities always belong, and Excluded Identities never do. For example, you might exclude the Administrator.
Who Can Members Request For?
Everyone , or
Specific Users , matching all or any of these criteria:
- Share attributes with the requester , such as the same department
- Report to the requester , meaning direct reports or all subordinates, with a maximum hierarchical depth
Match custom criteria , a filter parsed as a Velocity template with a requester parameter, for example manager.name == "$requester.manager.name"
Match filter rule , an IdentityFilterGenerator rule that returns a Filter (creating one requires the ManageRules SPRight)
Ignore scoping disregards IdentityIQ scopes for this purpose.
What Can Members Request or Remove?
Rules can limit the roles , applications , and entitlements members may request. A matching set of rules limits what they may remove . Sync with Request copies the request settings to the remove settings.
QuickLinks Tab
Enable the QuickLinks this population receives. For links that support it, use Configure to set options such as whether the link can be used for oneself.
What a Population Looks Like in XML
The documentation's example shows a DynamicScope that makes a link visible to anyone in the IT department or anyone with the Help Desk capability, and always to one named identity: <DynamicScope name="MyDynamicScope">
- <Inclusions>
- <Reference class="sailpoint.object.Identity" name="Barbara.Wilson"/>
- </Inclusions>
- <PopulationRequestAuthority allowAll="true"/>
- <Selector>
- <IdentitySelector>
- <MatchExpression>
- <MatchTerm name="capabilities" value="Help Desk Personnel"/>
- <MatchTerm name="Department" value="IT"/>
- </MatchExpression>
- </IdentitySelector>
- </Selector>
- </DynamicScope>
Read it piece by piece:
Inclusions is the UI's Included Identities list. Barbara Wilson sees the link whatever her department or capabilities.
Selector / IdentitySelector is the Membership rule. Here it is a Match List of a capability and an identity attribute.
PopulationRequestAuthority is Who can members request for? allowAll="true" means everyone.
The matching QuickLinkOptions object is what attaches this DynamicScope to a specific QuickLink, for example Access Reviews . Editing a population in the UI updates these objects for you. Seeing the XML helps when you promote populations between environments (section 3.1) or diagnose them in the Debug pages.
Design Examples
- Population Membership Request for QuickLinks
- Self Service All Only themselves (allowSelf) Request Access, Manage Passwords, Track My Requests
Manager Match List: identities with direct reports, or the Manager capability Report to the requester, direct reports Request Access, Manage Accounts, Edit Identity
- Help Desk Workgroup or capability based Everyone Manage Passwords, Manage Accounts, Create Identity
- MFA Contractors Match List: type = Contractor No one None (used only to enable an MFA workflow)
The last row reflects a documented tip. When a population is used to enable multi-factor authentication (section 3.3), create a separate population with "No one" as request authority, so MFA membership does not accidentally grant request rights.
Exam Traps
A population controls visibility and request authority . It does not grant SPRights. Capabilities still control administrative pages.
If a user can see Request Access but the target list is empty, check Who can members request for?
If a new custom QuickLink is invisible to everyone except administrators, it has no population attached.