SailPoint IdentityIQ architecture connects enterprise identity data, governance processes, and access changes within a customer-hosted platform. Its main building blocks include application services, a database, Identity Cubes, application integrations, background tasks, rules, workflows, and provisioning services.
Understanding how these components work together helps teams design reliable onboarding, access reviews, role changes, and offboarding processes.
Key Takeaways
- IdentityIQ combines a deployment architecture with a processing architecture. Servers and databases support the service; aggregation, refresh, workflows, and provisioning drive its behavior.
- Identity Cubes represent managed identities. Application accounts are associated with identities through account records known as Links.
- Aggregation and correlation answer different questions. Aggregation collects account information; correlation establishes which identity owns an account.
- Identity refresh processes information already available to IdentityIQ. Its selected options determine which calculations and downstream actions occur.
- Workflows coordinate a process; rules supply specific logic. Keeping those responsibilities clear makes implementations easier to maintain.
- Provisioning must be verified. An approved request does not establish that the target application has changed.
- Configuration matters. Connector capabilities, task settings, licensed features, and product versions affect the final behavior.
Introduction to SailPoint IdentityIQ Architecture
An employee changes departments in the HR system. Later, their identity attributes update in IdentityIQ, a lifecycle process starts, and changes are sent to connected applications.
That sequence may look like one automated action to the business. Behind it are several separate processes, each with its own responsibilities and possible failure points.
A useful architecture makes those boundaries clear. Teams should be able to explain where information originated, how accounts were matched, which decision triggered a change, and whether the destination system accepted it.
This guide focuses on those relationships. It explains the logical components and processing flows rather than prescribing a single production topology. Infrastructure sizing and supported software must follow the requirements for the IdentityIQ version being deployed.
If you are new to the topic, start with our guide to Identity and Access Management fundamentals. For a product overview before exploring the architecture, read about SailPoint IdentityIQ features and benefits.
Overview of IdentityIQ Core Components
SailPoint IdentityIQ has two related architectural views.
The deployment view covers the application environment, database, connectivity, and operational services. The logical view explains how identity information moves through governance and access processes.
Application Services and User Interface
Employees, approvers, reviewers, and administrators interact with IdentityIQ through its web application.
Application services support activities such as submitting requests, recording approvals, reviewing access, and managing configuration.
Production designs need to consider availability and capacity across both interactive activity and background processing. The appropriate arrangement depends on workload and supported deployment options.
Database and Persistent Records
The database stores persistent application data, including identity information, configuration, and applicable process records.
Its performance affects the wider service. Slow database operations can contribute to delays in tasks, requests, and reviews.
Backup and recovery planning should address the application and database together so that a restored environment is consistent and usable.
Connectors and Applications
An IdentityIQ Application defines how the platform communicates with an enterprise system.
It includes connector-specific settings, account schemas, correlation configuration, and other relevant options.
A connector may support reading data, changing data, or both. Teams need to establish its actual capabilities before designing automated fulfillment around it.
Tasks, Rules, Workflows, and Provisioning
These components perform different jobs:
| Component | Main Responsibility | Example |
|---|---|---|
| Application services | Support interactive and application processing | Display an access request and record an approval |
| Database | Store persistent application information | Retain identity and configuration records |
| Application configuration | Describe connectivity and data interpretation | Define account attributes and matching logic |
| Connector | Communicate with a specific system | Read directory accounts or perform supported updates |
| Background task | Execute a configured processing activity | Run account aggregation or identity refresh |
| Rule | Apply logic at a supported extension point | Handle a specialized account-matching condition |
| Workflow | Coordinate steps in a business process | Route an approval before provisioning |
| Provisioning services | Prepare and route account or permission changes | Send an approved group-membership update |
These are logical responsibilities. They should not be interpreted as a requirement to deploy a separate server for every row.
Understanding Identity Cubes and Applications
Identity Cubes and Applications provide the foundation for understanding who has access to what.
The Identity Cube represents the managed identity. Application account information describes that identity’s presence in connected systems.
What an Identity Cube Contains
An Identity Cube brings together information associated with a managed identity, such as:
- Identity attributes, including department and manager.
- Associated application accounts.
- Roles and entitlements.
- Policy and risk information.
- Other configured governance data.
It is a logical identity model within IdentityIQ, rather than a separate database or physical appliance.
For example, one employee may have accounts in a directory, an expense platform, and a finance application. The Identity Cube provides a consolidated identity context for those accounts.
How Account Links Relate to Identities
IdentityIQ uses Link objects to represent application account information associated with an identity.
This distinction helps during troubleshooting. A value on an application account record may differ from a mapped identity attribute, depending on source data and processing.
When investigating an unexpected department or account status, check both the source account information and the identity-level value.
SailPoint’s documentation on updating the Identity Cube explains how account information and provisioning results are reflected in the model.
Authoritative and Non-Authoritative Applications
An authoritative application provides information used to establish identities. An HR source is a common example for employees.
Other applications provide accounts that need to be associated with those identities.
Application design also needs to establish which source controls each identity attribute. An authoritative designation alone does not resolve conflicting values across every connected system.
SailPoint’s application configuration documentation describes the authoritative application setting.
Account Aggregation and Identity Correlation
Aggregation brings information into IdentityIQ. Correlation establishes the identity associated with an account.
Treating them as separate responsibilities helps teams investigate whether a problem came from missing source data or incorrect ownership matching.
Account Aggregation Reads Source Information
Account aggregation retrieves data from configured applications.
The information collected depends on the connector and schema. It may include account identifiers, account status, attributes, and entitlement values such as group memberships.
Account group aggregation handles group and related application-object information where supported.
SailPoint’s aggregation overview explains how applications and tasks work together to collect this data.
Correlation Matches Accounts to Identities
Correlation uses configured mappings, conditions, or rules to associate accounts with identities.
A stable employee identifier is often more dependable than a display name. Names can change, and different people can share the same name.
Matching logic should handle missing values and ambiguous results deliberately. A confident-looking match to the wrong person can be harder to identify than an account left unmatched.
Uncorrelated Accounts Need Investigation
An unmatched account may belong to an employee whose source record is missing, a contractor, a service account, or someone who has left.
It may also reflect inconsistent identifiers.
Do not assume every uncorrelated account should be assigned to the closest name match. Establish ownership first, then correct the data or correlation configuration.
SailPoint’s application concepts documentation describes correlation approaches and manual account association.
Aggregation Is Not a Guarantee of Current Source Data
IdentityIQ’s view depends on the last successful collection and subsequent processing.
If an aggregation fails or excludes records unexpectedly, downstream reviews may use incomplete information.
Monitor task completion, errors, and unusual account-count changes before relying on a collection as the basis for access decisions.
Identity Refresh and Lifecycle Processing
Identity refresh processes identity information within IdentityIQ according to the selected task options.
It is distinct from aggregation: aggregation reads source data, while refresh evaluates and updates aspects of the identity model using available information.
What Identity Refresh Can Process
Depending on its configuration, refresh can update identity attributes, evaluate role information, check policies, update risk information, synchronize attributes, or initiate configured processing.
These actions do not all occur simply because a task is named “Identity Refresh.”
The selected options define its behavior, including whether provisioning-related actions are enabled.
Full and Targeted Refresh
A refresh may process a broad identity population or a selected subset.
Changed-identity processing can reduce unnecessary work, but its scope needs careful planning. A change to policy or role logic may affect identities whose account data has not changed.
The task population should match the purpose of the refresh.
How Lifecycle Processing Fits In
A lifecycle process may respond to a new identity, a departure, or a change in an attribute such as manager or department.
For a transfer, the design should establish which change triggers evaluation, which permissions are reconsidered, and which workflow handles the result.
Do not assume that detecting a department change automatically removes every entitlement associated with the previous department.
SailPoint’s Identity Refresh documentation details the available options and their effects.
| Process | Primary Purpose | Typical Result |
|---|---|---|
| Aggregation | Read account and related data from an application | Updated source information in IdentityIQ |
| Correlation | Associate accounts with identities | Account ownership represented in the identity model |
| Identity refresh | Evaluate and update configured identity information | Updated attributes, roles, policies, or configured downstream actions |
| Lifecycle processing | Respond to defined identity events | A business process starts for the relevant change |
| Provisioning | Carry out supported account or permission changes | Updates sent to target systems or fulfillment tasks |
Rules and Workflows in IdentityIQ
Rules and workflows both support customization, but they have different responsibilities.
A rule supplies logic at a particular point. A workflow coordinates a sequence of actions.
Rules Apply Specific Business Logic
IdentityIQ rules can customize supported processing points, such as account correlation, data validation, and provisioning behavior.
SailPoint documents BeanShell as a language used for these rules.
Custom logic should have a clear purpose, defined inputs, and expected outputs. It also needs to handle missing data and errors without exposing sensitive information in logs.
See SailPoint’s rules and scripts documentation for the relationship between standalone rules and embedded scripts.
Workflows Coordinate Business Steps
IdentityIQ uses the terms business process and workflow for connected sequences of actions.
A workflow might collect request information, evaluate conditions, request approval, invoke provisioning, and send a notification.
The workflow definition describes the process. A WorkflowCase represents a running instance and its state.
Triggers and Approval Behavior Depend on Configuration
Access requests, lifecycle events, attribute changes, and other configured activities can initiate workflows.
Some processes require approval; others may follow an approved policy without an interactive decision.
Teams should document which events can start a workflow and which paths can change access.
SailPoint’s workflow basics documentation explains these concepts and common triggers.
Keep Customization Maintainable
Before adding custom code, check whether supported configuration meets the requirement.
Where customization is needed, separate reusable logic from process orchestration. Document dependencies and include the relevant rules and workflows in upgrade testing.
Provisioning and Access Request Architecture
An access request captures a desired change. Provisioning prepares and routes the work needed to carry it out.
Between those stages, the implementation may apply approvals, policy checks, forms, or other configured steps.
Requests Become Provisioning Plans
IdentityIQ represents requested changes in provisioning plans.
A plan can include operations affecting accounts or permissions across multiple applications.
It describes the intended changes; it does not prove that those changes have already occurred.
The Provisioning Broker Prepares and Routes Work
The Provisioning Broker evaluates and compiles plans for processing.
A request involving several applications may be divided into application-specific plans and routed to the appropriate handlers.
This creates a practical need to track outcomes per application. A request can involve one successful change and another that still requires attention.
Fulfillment Can Be Automated or Manual
A supported read-write connector may perform the change directly. Another integration may handle it, or IdentityIQ may create a manual work item.
The fulfillment method depends on the application and configuration.
SailPoint’s provisioning overview describes this processing path.
Verification Completes the Process
Confirmation mechanisms differ between integrations. Some results become available through connector processing; others require subsequent aggregation or another confirmation step.
An illustrative request might follow this path:
- An employee requests finance reporting access.
- The configured process checks the request and obtains approval.
- A provisioning plan describes the required change.
- The plan is prepared and routed to the fulfillment method.
- The target change is performed.
- The outcome is checked and outstanding failures are resolved.
Approval, submission, and verified fulfillment should remain distinguishable in operational reporting.
Access Certifications and Governance
Certifications use IdentityIQ’s access information to support review decisions.
Their quality depends on accurate collection, correct correlation, and understandable entitlement descriptions.
Understanding how identity governance fits within IAM helps clarify the role certifications play in the wider access lifecycle.
Define the Review Scope and Owners
A certification establishes what is being reviewed, who should review it, and the applicable process.
Managers may understand job responsibilities, while application owners understand the meaning of particular permissions. The review design should account for those differences.
Present Access in Understandable Terms
A technical group name may be accurate but unhelpful to a business reviewer.
Descriptions should explain what the access permits, who owns it, and any relevant sensitivity. This context makes approval or revocation decisions more meaningful.
Follow Revocations Through to Completion
A reviewer’s decision can initiate corrective action, but fulfillment depends on the configured integration.
Teams need visibility into failed removals and manual tasks that remain open.
SailPoint’s certification documentation explains review actions and automated or manual remediation.
Organizations planning these processes can explore Eshiam’s SailPoint IdentityIQ services.
IdentityIQ Architecture Best Practices
A reliable architecture makes routine processing predictable and failures visible.
Design Around the Deployed Version
Confirm supported infrastructure, connector requirements, and available task options against the documentation for your release.
A logical guide provides context, but it should not replace version-specific deployment requirements.
Establish Clear Sources of Truth
Document which systems control important attributes and how conflicting or missing values are handled.
Test duplicate identifiers, name changes, rehires, and identities with multiple accounts.
Schedule Tasks Around Their Dependencies
Plan collection and processing in an order that produces the required identity state before downstream decisions.
Avoid unnecessary overlap between heavy tasks. Test partitioning and concurrency with the intended provisioning behavior rather than enabling them solely to increase speed.
Protect Integration and Administrative Access
Use appropriately limited service credentials, protect secrets, and restrict administrative capabilities.
Review who can change correlation rules, workflows, provisioning settings, and other configurations that affect access decisions.
For privileged credentials and administrative sessions, explore Eshiam’s Privileged Access Management services.
Monitor Processing and Business Outcomes
Infrastructure metrics matter, but so do operational results:
- Failed or delayed aggregations.
- Unexpected changes in account volumes.
- Uncorrelated accounts requiring investigation.
- Refresh failures and processing backlogs.
- Provisioning failures.
- Overdue manual fulfillment.
- Revocations awaiting confirmation.
SailPoint’s Administrator Console documentation describes tools for examining operational activity.
Test Recovery and Partial Failures
Include unavailable applications, interrupted tasks, rejected changes, and failed integrations in testing.
Recovery should avoid duplicate actions and make unresolved work visible. Backup procedures also need a tested restoration process.
Maintain Ownership After Go-Live
Assign responsibility for application integrations, task schedules, rules, workflows, and operational exceptions.
Requirements change after deployment. Regular maintenance keeps the architecture aligned with the business.
Eshiam’s managed services provide an option for organizations seeking ongoing operational support.
Conclusion
SailPoint IdentityIQ architecture connects source information, identity models, governance decisions, and access fulfillment.
The most useful design is one your team can trace: where the data came from, which identity owns the account, what triggered the decision, how the change was delivered, and whether it succeeded.
Clear boundaries between aggregation, correlation, refresh, workflows, and provisioning make that traceability possible. They also make failures easier to investigate before they become lasting access gaps.
Planning or improving an IdentityIQ deployment? Contact Eshiam to discuss your architecture and implementation requirements.





