> ## Documentation Index > Fetch the complete documentation index at: https://panaptico.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Identity Links: Resolve Entities Across Systems > Identity Links resolve the same entity across identity, cloud, network, and endpoint systems so verification can target real operators, devices, and resources. Identity Links are Panaptico's cross-system entity resolution layer. An operator might exist as a user in Okta, a device record in Intune, and a seat in Cloudflare. Without linking, these are three separate objects. Identity Links resolve them into one entity so verification can target the real operator, not a fragmented record. Groups then define named, verifiable populations like "Japan Office" or "Main Admin Users." ## How Identity Links work Panaptico reads entity data from each connected system via System Sensors. It matches records using correlation keys: email, device ID, serial number, IP address, or other stable identifiers. When a match is confident, the records are linked. When confidence is low, the Atlas flags the candidate for review. Once linked, the entity carries all of its attributes from every source. A single device record might include: * Okta: user assignment and MFA status * Intune: compliance state and OS version * Cloudflare: network location and WARP enrollment * MDM: encryption and patch level This unified view is what makes cross-system Signals and Initiatives possible. ## Groups as verifiable scopes Groups turn populations into named, reusable scopes for verification. Examples include: * **Japan Office** — all devices and users physically located in the Tokyo office * **Main Admin Users** — all accounts with super-admin privileges across identity systems * **Production Databases** — all database instances tagged in cloud provider consoles Groups are not static lists. They are queries against the live Atlas, so membership updates automatically as the estate changes. When you verify an Initiative against a Group, you are always verifying the current population, not a stale export. ## When to use Identity Links Use Identity Links when your verification must span multiple systems and you need to reason about real entities, not siloed records. They are required for any cross-system Signal, Enriched Signal, or Initiative that involves identity, device, or network scope. The live map of entities, relationships, and dependencies that powers linking. The readers that ingest the raw entity data used for linking. Apply verification to named Groups as part of budget-level programs.