Is this a valid scenario that can be achieved in IdentitylQ by configuring the Quicklink populations? Solution: Allow a user to create a new identity…

The creation of an Identity Cube is a core administrative function within IdentityIQ, not a user-facing, self-service action. Identity Cubes are generated and updated by the system during aggregation tasks that pull data from authoritative sources (e.g., an HR system). Quicklinks are user interface shortcuts to existing functionalities, and Quicklink populations control the visibility of these shortcuts. Since there is no built-in functionality for a user to manually create an Identity Cube via the UI, a Quicklink cannot be configured to perform this action.

A. Yes: This is incorrect because Identity Cube creation is a backend administrative process tied to data aggregation, not a user-initiated task that can be exposed through a Quicklink.

1. SailPoint IdentityIQ 8.2 - Administration Guide: In the section "Building the Identity Cubes," it is explained that "Identity Cubes are created and refreshed by running an aggregation task from an authoritative application." This confirms that cube creation is a result of a scheduled or manually run administrative task, not a user-facing action. (Reference: Chapter on Identity and Account Aggregation).

2. SailPoint IdentityIQ 8.2 - User Interface Customization: The guide describes Quicklinks as "links that can be configured to appear on the home page and in the main menu to provide users with easy access to frequently used areas of the product." It further explains that populations are used to "determine who can see the QuickLink." This documentation establishes that Quicklinks provide access to existing features, but do not create new core functionalities like identity creation. (Reference: Chapter on QuickLink Configuration).

3. SailPoint IdentityIQ Concepts Guide (Internal Training Material): The concept of the Identity Cube is introduced as the central data model for an identity, populated through aggregation. The lifecycle of an identity (creation, modification, deletion) is consistently described as being driven by data feeds from authoritative systems, managed through aggregation tasks, not through direct user interaction via the dashboard.