What Is SailPoint IdentityIQ? Features, Architecture and Benefits

SailPoint IdentityIQ is a customer-hosted identity governance and administration (IGA) solution that helps enterprises understand, manage, and review access across their applications and systems. It brings identity information, access requests, lifecycle processes, certifications, and policy checks into a coordinated governance program.

Key Takeaways

  • IdentityIQ focuses on identity governance. It helps organizations establish who has access, why they have it, and whether it remains appropriate.
  • The Identity Cube brings identity information together. It connects a person’s attributes with accounts, permissions, and other governance information.
  • Aggregation reads access information; provisioning changes it. Keeping these processes working reliably is essential to accurate governance.
  • Access reviews need follow-through. A decision to revoke access must result in the permission being removed from the target system.
  • IdentityIQ is customer-hosted. Organizations need to plan for infrastructure, maintenance, upgrades, and operational ownership.
  • IdentityIQ and Identity Security Cloud have different delivery models. The right choice depends on business requirements, integration needs, and operational capabilities.

Managing access becomes harder as a business grows. One employee may hold accounts in a directory, an HR platform, a finance application, and several internal systems. Each application shows part of the picture.

The difficulty comes when someone asks a broader question: does this person still need everything they can access?

SailPoint IdentityIQ helps enterprises answer that question and act on the result. This guide explains how it works, the components behind it, and when it may be worth considering.

What Is SailPoint IdentityIQ?

SailPoint IdentityIQ is an enterprise platform for governing digital identities and their access to connected applications.

Its purpose goes beyond maintaining a list of accounts. IdentityIQ helps organizations connect accounts to their owners, understand permissions, route access decisions to the right people, and carry out approved changes.

For example, an employee may have three application accounts with different usernames. IdentityIQ can bring those accounts together under one identity, provided the organization has configured reliable matching rules.

That consolidated view helps a manager or application owner review the employee’s access as a whole.

Where IdentityIQ Fits Within Enterprise Security

IdentityIQ supports the broader discipline of Identity and Access Management, with a particular focus on governance and administration.

An authentication platform establishes who is signing in. IdentityIQ helps determine whether that person should receive or retain particular permissions.

Organizations commonly use it alongside identity providers, application security controls, and privileged access tools. Each has a different responsibility.

Eshiam’s SailPoint IdentityIQ services support organizations implementing and managing these governance processes.

How Does SailPoint IdentityIQ Work?

IdentityIQ collects identity and account information, connects accounts to people, evaluates access, and manages governance workflows.

A useful way to follow the process is to start with the information coming in and finish with changes being confirmed in the destination application.

Collect Identity and Account Information

IdentityIQ connects to configured sources, such as HR systems, directories, and business applications.

It reads available information through aggregation. Depending on the application, that may include account identifiers, employee attributes, group memberships, and entitlements.

The information available depends on the source, connector capabilities, and configuration.

Connect Accounts to the Right Identity

Account correlation associates application accounts with the identities that own them.

An employee number or another dependable identifier can help establish that connection. Matching solely on inconsistent names or email formats can create mistakes.

Accounts that cannot be matched need investigation. They may represent legitimate exceptions, service accounts, or access that no longer has an accountable owner.

SailPoint’s application concepts documentation explains aggregation, correlation, and provisioning.

Evaluate Access and Start Workflows

Once information is available, configured processes can evaluate roles, lifecycle changes, and policy conditions.

An employee joining a department might qualify for baseline access. Another request may need approval from a manager or application owner.

IdentityIQ workflows coordinate those steps according to the implementation’s rules.

Carry Out Approved Changes

Approved changes become provisioning requests.

Where supported, a read-write connector can update the target application. Other changes may pass through an integration or become manual work items.

A connected application is not automatically an application that supports every provisioning action. Teams need to confirm the operations each integration can perform.

Confirm Results and Review Access

The process needs to establish whether the requested change happened.

Depending on the integration, confirmation may involve connector results, subsequent aggregation, or completion of a manual task.

This distinction is especially important during offboarding. An approved removal request and a removed permission are two different stages.

Key Features of SailPoint IdentityIQ

IdentityIQ brings together capabilities for understanding access, managing changes, and reviewing whether permissions remain appropriate. Availability depends on the organization’s licensed capabilities, product version, and configuration.

Identity Warehouse and Identity Cubes

The Identity Warehouse provides access to identity records.

An Identity Cube is the logical representation of a managed identity. It can bring together attributes, linked accounts, entitlements, roles, policy violations, and risk information.

It gives reviewers useful context. Instead of assessing an isolated account, they can examine access associated with the person who owns it.

SailPoint’s identity management documentation describes the Identity Cube and Identity Warehouse.

Access Requests and Approvals

Users can request access through configured processes, with approvals routed according to business requirements.

A useful implementation makes the choices understandable. Requesting “Finance Reporting — Read Only” is easier to assess than an unexplained technical entitlement code.

Approval rules also need clear ownership so requests reach someone qualified to make the decision.

Identity Lifecycle Management

Lifecycle processes respond to events such as joining the organization, changing responsibilities, or leaving.

The workflow may create accounts, update attributes, request approvals, or remove access.

A transfer deserves particular attention. Adding new permissions is only part of the change; the organization must also decide which existing permissions should end.

Access Certifications

Certifications organize access reviews for designated reviewers.

Managers, application owners, or other accountable people review permissions and decide whether they remain necessary.

The quality of the review depends on the information presented. Clear descriptions and business context help reviewers make decisions they can explain.

SailPoint’s access certification documentation explains review capabilities and remediation options.

Role Management

Roles group permissions into units that reflect responsibilities or technical access patterns.

This can make requests and reviews easier to manage. For instance, a defined finance reporting role can represent an approved set of permissions across relevant applications.

Roles still need owners and periodic review. A role that grows without scrutiny can distribute unnecessary access widely.

Policy and Separation-of-Duties Checks

Policy checks help identify access combinations that conflict with organizational requirements.

A separation-of-duties policy might flag someone who can both create a supplier and approve payments to that supplier.

Detecting the conflict is the beginning. The organization must decide how to remove it or document and govern an approved exception.

Provisioning and Operational Tracking

Provisioning translates approved decisions into account and permission changes.

Operational tracking helps administrators identify failures, pending manual actions, and changes requiring attention.

SailPoint’s provisioning overview explains how provisioning plans are processed and routed.

FeatureWhat It DoesPractical Value
Identity CubesBring identity and linked account information togetherHelp teams understand a person’s access across connected systems
Access requestsRoute requests through configured approval processesMake access decisions more consistent and traceable
Lifecycle managementRespond to approved identity changesSupport onboarding, transfers, and departures
CertificationsOrganize reviews of existing accessHelp identify permissions that are no longer justified
Role managementGroup related permissionsSimplify access assignment and review
Policy checksIdentify defined conflicts or violationsSupport investigation and remediation
Provisioning trackingRecord the progress of access changesHelp teams resolve failed or incomplete actions

SailPoint IdentityIQ Architecture Explained

IdentityIQ architecture combines a web application, governance processes, persistent data storage, and integrations with enterprise systems.

The following is a conceptual explanation. The actual topology, supported software, and sizing must follow the requirements for the deployed IdentityIQ version.

User Interface and Application Services

Employees, reviewers, and administrators interact with IdentityIQ through its application interface.

Behind that interface, application services process requests, approvals, certifications, and administrative actions.

Access to IdentityIQ itself also needs appropriate controls. A reviewer should receive the capabilities required for their work without unnecessary administrative authority.

Identity Data and Database

The database stores IdentityIQ’s persistent application data, including configuration and identity governance records.

Identity Cubes provide a logical view of identity information within that environment. They are part of the application’s data model, rather than separate physical appliances.

Database performance and reliable backups affect the operation of the wider service.

Connectors and Integration Paths

Connectors allow IdentityIQ to communicate with configured applications.

Some integrations read account and entitlement information. Others also support creating, updating, disabling, or deleting accounts and changing permissions.

Capabilities vary. Integration design must establish what can be read, what can be changed, and how results will be verified.

Workflow, Policy, and Provisioning Processing

Configured workflows coordinate business steps such as approval, notification, and fulfillment.

Policies evaluate defined access conditions. Provisioning processing prepares and routes changes to the appropriate destination or fulfillment method.

These functions work together, but they serve different purposes: deciding what should happen, arranging the work, and executing the change.

Background Tasks and Operational Monitoring

Tasks handle activities such as aggregation and identity refresh.

Scheduling needs to account for application limits, identity volumes, and competing workloads. For example, running several large aggregations alongside a major certification campaign may require different capacity planning from routine daily processing.

SailPoint’s environment monitoring documentation identifies operational measures including task threads, memory use, and database response time.

Architecture ComponentMain ResponsibilityPlanning Consideration
Application servicesProcess user and administrative activityAvailability, capacity, and administrative access
DatabaseStore persistent application and governance dataPerformance, backup, recovery, and data protection
Connectors and integrationsRead information and carry out supported changesConnectivity, credentials, supported actions, and failure handling
Workflows and policiesCoordinate decisions and evaluate access conditionsClear ownership, testing, and maintainability
Background tasksRun aggregation, refresh, and other scheduled processingTiming, workload, and monitoring
Provisioning processingRoute approved access changesFulfillment method and result verification

Identity Governance and Administration in IdentityIQ

Identity governance asks whether access is appropriate. Administration puts the approved decision into effect.

IdentityIQ connects these responsibilities through identity information, policies, workflows, and fulfillment processes.

Make Access Ownership Clear

Every application and sensitive permission needs someone accountable for its use.

That ownership helps determine who approves requests, reviews existing access, and resolves exceptions.

Without it, the platform can route work efficiently while still sending decisions to people who lack the necessary context.

Review Access with Business Context

A useful access review explains what a permission allows and how it relates to the user’s responsibilities.

Managers may understand a person’s role, while application owners understand the consequences of specific entitlements. Review design should reflect those differences.

Connect Decisions to Remediation

A review finding matters only when the required action follows.

If a reviewer revokes access, the process must route the removal, handle failures, and confirm the outcome.

SailPoint’s certification remediation documentation explains how certification decisions can generate provisioning requests.

Benefits of SailPoint IdentityIQ for Enterprises

IdentityIQ’s benefits depend on the coverage and quality of the implementation. Connecting an application is useful; maintaining reliable data and actionable processes makes that connection valuable.

Build a More Complete View of Access

Bringing linked accounts together makes it easier to investigate permissions across systems.

Teams can identify access that would be difficult to recognize from individual application reports alone.

Reduce Repetitive Access Administration

Defined lifecycle processes and provisioning integrations can reduce repeated manual work.

Administrators can spend more time resolving exceptions and improving integrations rather than recreating the same routine changes.

Make Reviews More Consistent

Certifications give access reviews a defined scope, reviewer, and schedule.

They also provide a way to record decisions and track corrective action, reducing dependence on scattered spreadsheets and email threads.

Support Audit and Control Evidence

Requests, approvals, review decisions, and provisioning records help explain how access was governed.

They support control assessments, although using IdentityIQ does not by itself establish regulatory compliance.

Accommodate Customer-Controlled Deployment Requirements

IdentityIQ’s customer-hosted model gives organizations responsibility for their deployment environment.

That can be relevant where hosting control or specific enterprise integration requirements influence the decision. It also creates an ongoing need for maintenance, security updates, and recovery planning.

SailPoint IdentityIQ Use Cases

The following scenarios illustrate how IdentityIQ capabilities can be applied. They are examples, rather than claims about specific Eshiam customer projects.

Employee Onboarding

An approved employee record enters the process before the start date.

Configured policies and workflows determine baseline access, obtain any necessary approvals, and route account creation to connected applications or manual fulfillment teams.

Internal Transfers

An employee moves from procurement to operations.

The organization provides approved operations access and reassesses procurement permissions. Any removal depends on the configured process and supported fulfillment paths; a role change does not automatically guarantee that every old entitlement disappears.

Employee and Contractor Offboarding

A departure triggers access removal activities.

Teams track failures and exceptions, then verify the result in relevant systems. Session termination and token revocation may require separate controls in the applications or identity provider.

Periodic Access Reviews

Application owners review access to a sensitive finance system.

They confirm justified permissions, revoke unnecessary access, and resolve identified policy conflicts. The remediation process then follows those decisions through to completion.

Separation-of-Duties Management

A configured policy identifies a conflicting permission combination.

The responsible owner investigates whether to remove access or establish an approved exception with appropriate oversight.

Governance Across Mixed Application Environments

An enterprise needs to review access across modern cloud applications and older internal systems.

IdentityIQ can coordinate governance for configured integrations, while each application’s connector and fulfillment capabilities determine the degree of automation available.

When Should Businesses Implement SailPoint IdentityIQ?

IdentityIQ may be worth evaluating when access governance has become difficult to manage consistently across the organization.

The decision should consider both the access problem and the capacity to operate a customer-hosted platform.

When Access Reviews Depend on Spreadsheets

If reviewers spend more time reconciling reports than assessing permissions, the organization may need a more coordinated review process.

The first requirement is dependable application data—not simply moving the spreadsheet into a different interface.

When Lifecycle Changes Leave Access Gaps

Delayed onboarding, incomplete transfers, and uncertain offboarding indicate that access processes need attention.

IdentityIQ can help coordinate these changes when source data, application integrations, and ownership are in place.

When Applications Need Shared Governance

Different application teams may use inconsistent approval and review practices.

A common governance program can establish clearer expectations while preserving application-specific requirements.

When Customer-Hosted Deployment Is a Requirement

Some organizations need direct control over hosting and operating their identity governance environment.

Before choosing IdentityIQ, establish who will handle infrastructure, database administration, upgrades, testing, and service recovery. Eshiam’s managed services provide an option for ongoing operational support.

When Comparing IdentityIQ with Identity Security Cloud

IdentityIQ and Identity Security Cloud address identity security through different delivery models. SailPoint identifies IdentityIQ as customer-hosted and Identity Security Cloud as SaaS in its published company information.

A hosted IdentityIQ deployment does not become Identity Security Cloud simply because its servers run in a cloud environment.

ComparisonSailPoint IdentityIQSailPoint Identity Security Cloud
Delivery modelCustomer-hosted softwareSailPoint-delivered SaaS
Platform operationsCustomer or service provider operates the deployed environmentSailPoint operates the SaaS platform; customers manage tenant configuration and relevant integrations
UpdatesRequire planning and deployment for the customer-hosted environmentPlatform updates follow the SaaS delivery model
Implementation focusDeployment architecture, integrations, workflows, and ongoing maintenanceTenant configuration, integrations, governance processes, and applicable connectivity components
Evaluation prioritiesHosting requirements, operating capacity, integration needs, and maintainabilitySaaS suitability, available capabilities, integration needs, and operating model

Feature availability and commercial scope should be checked separately for each product. They are distinct platforms, so a move between them requires assessment rather than assuming a direct configuration transfer.

Organizations exploring the SaaS option can review Eshiam’s Identity Security Cloud services.

Conclusion

SailPoint IdentityIQ helps enterprises bring access information, decisions, and administrative processes into a coordinated governance program.

Its value comes from the connections between those activities: matching accounts accurately, presenting permissions clearly, routing decisions to accountable owners, and confirming that approved changes happen.

Before implementation, define the access problems you need to solve and the operating responsibilities you can support. Then test a manageable group of applications before expanding.

Evaluating IdentityIQ for your organization? Contact Eshiam to discuss your identity governance requirements.

Frequently Asked Questions About SailPoint IdentityIQ

What Is SailPoint IdentityIQ Used For?

SailPoint IdentityIQ is used to govern identities and access across enterprise applications. It helps organizations connect accounts to their owners, manage access requests, coordinate lifecycle changes, review permissions, and identify policy conflicts. Its effectiveness depends on reliable identity data and configured application integrations.

Is SailPoint IdentityIQ an IAM or IGA Solution?

SailPoint IdentityIQ is primarily an Identity Governance and Administration solution within the broader IAM discipline. It focuses on whether access is appropriate, approved, and still needed. It commonly works alongside identity providers and other systems responsible for authentication, single sign-on, and application access enforcement.

What Are the Main Features of IdentityIQ?

IdentityIQ capabilities include identity aggregation and correlation, Identity Cubes, access requests, lifecycle workflows, certifications, role management, policy checks, and provisioning. The capabilities available to an organization depend on its product version, licensing, connector support, and implementation configuration.

How Does SailPoint IdentityIQ Work?

IdentityIQ reads information from configured sources, associates application accounts with identities, and uses that information in governance processes. Requests, lifecycle events, and review decisions can initiate access changes. Those changes are fulfilled through supported connectors, integrations, or manual tasks, with results verified through the applicable process.

What Is the Difference Between SailPoint IdentityIQ and Identity Security Cloud?

IdentityIQ is customer-hosted software, while Identity Security Cloud is delivered as SaaS. This changes responsibilities for platform operation, upgrades, and implementation. Both support identity security, but their capabilities and configuration approaches should be evaluated separately. Hosting IdentityIQ on cloud infrastructure does not make it Identity Security Cloud.

What Is an Identity Cube in SailPoint IdentityIQ?

An Identity Cube is IdentityIQ’s logical representation of a managed identity. It brings together attributes, linked application accounts, permissions, roles, and other governance information. This consolidated view helps reviewers and administrators understand access associated with an identity across configured sources.

What Is Aggregation in SailPoint IdentityIQ?

Aggregation is the process of reading account and related access information from a configured source into IdentityIQ. The information collected depends on the application and connector configuration. Aggregation supports visibility and review; provisioning is the separate process used to carry out supported changes in target systems.

How Does IdentityIQ Access Certification Work?

Access certification presents a defined set of permissions to designated reviewers. They assess whether access remains appropriate and approve it or request corrective action. Revocations are fulfilled through configured automated or manual processes, so teams need to confirm that review decisions result in the required changes.

Can SailPoint IdentityIQ Automate Provisioning and Deprovisioning?

IdentityIQ can automate supported account and permission changes when the required workflows and integrations are configured. Some applications require manual fulfillment or another provisioning system. Organizations must test each action, monitor failures, and verify removal rather than assuming every connector supports complete automated deprovisioning.

Can SailPoint IdentityIQ Be Deployed in the Cloud?

IdentityIQ can run in a customer-controlled cloud environment where the deployment meets the requirements of the relevant product version. It remains customer-hosted software. Infrastructure, security, maintenance, and upgrade responsibilities must still be assigned to the customer or its service provider.

Padmanabhaiah Kaipa

About the author

Padmanabhaiah Kaipa

Founder and Managing Director, Eshiam Software Pvt. Ltd.

Padmanabhaiah Kaipa is the Founder and Managing Director of Eshiam Software Pvt. Ltd. An IIT Kharagpur alumnus with more than 35 years of professional experience, he previously served as CEO of Askar Microns and Vigel Manufacturing Technologies. He leads Eshiam's business across enterprise identity security and software services.

Planning an identity security initiative?

Talk to Eshiam's SailPoint and IAM specialists about your requirements.

Contact Eshiam