> For the complete documentation index, see [llms.txt](https://docs.teleskope.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.teleskope.ai/the-platform/identity-view.md). # Identity View ## What is Identity View? Identity View gives you a centralized, searchable view of every identity that has access to your data — across all connected sources. Instead of hunting through individual connectors to understand who can access what, Identity View brings all of that context into one place. An identity is any user, service account, or external party that has been granted access to a resource that Teleskope has scanned. Identity View lets you understand the scope of that access — what data they can reach, how sensitive it is, and whether that access carries any risk. Identity View covers two types of identities: * **Human identities** — users identified by email address across SaaS connectors (Google Drive, SharePoint, Slack, etc.) * **Non-Human Identities (NHIs)** — service accounts, bots, and integrations that have access to your data but aren't associated with a person's email *** ## Navigating to Identity View 1. In the left-hand navigation, click **Identities** 2. You'll land on the **Identities overview page**, which gives a high-level summary of your identity landscape 3. From there you can drill into the **Identities list**, the **Non-Human Identities tab**, or the **Domains list** *** ## The Overview Page When you first land in Identity View, you'll see a summary of key signals across all your identities: * **Trust level breakdown** — a chart showing how many identities fall into each trust category (Internal, External, Personal, Non-Human) * **Top identities** — the identities with the broadest or most sensitive data access * **Top external or personal domains** — the external domains (e.g. gmail.com, contractor organizations) that have the most access to your data This overview is designed to help you quickly spot areas of elevated risk — for example, a high number of external identities with access to critical data. *** ## The Identities List The Identities list shows every human identity that has access to data in your connected sources. For each identity you can see: * **Email / identifier** — the identity's email address * **Type** — whether the identity is Internal, External, or Personal * **Trust level** — a classification of how trusted the identity is based on its relationship to your organization * **Max sensitivity** — the highest sensitivity level of any resource this identity has access to * **Resource count** — the number of resources the identity can access You can **search** for a specific identity by name or email, **filter** by type, trust level, or sensitivity level, and **sort** by any column to quickly surface the highest-risk identities. *** ## Identity Details Clicking any identity in the list opens a detail page with a deeper view of that specific identity's access. This includes: * **Sensitivity rollup** — a breakdown of how many resources the identity can access at each sensitivity level (Critical, High, Medium, Low) * **Data elements** — the types of sensitive data the identity has access to (e.g. SSN, credit card numbers, email addresses) * **Data categories** — the broader data categories covered (e.g. PII, PHI, PCI) * **Document types** — the types of files or resources in scope * **Data resources table** — a full list of every resource this identity has access to, with connector, sensitivity, and file path shown for each row From the data resources table you can search, filter, and export the list as a CSV. *** ## Organization Identity Settings Identity View's trust level classifications — Internal, External, and Personal — are determined by your **Internal Domains** configuration. This is what controls whether an identity shows up as a trusted internal user or as an external party in the overview chart, the identities list, and all access rollups. To view or update your internal domains: 1. Go to **Settings** in the left-hand navigation 2. Open **Organization Identity** and select the **Internal domains** tab 3. Add or remove the email domains that belong to your organization (e.g. `yourcompany.com`) Any identity whose email matches a configured internal domain is classified as **Internal**. Identities with personal email domains (e.g. `gmail.com`, `outlook.com`) are classified as **Personal**. All others are classified as **External**. If a colleague is showing up as External, it's likely because their email domain hasn't been added to your internal domains list. Updating this setting will re-classify all affected identities. This page is admin-only. *** ## Non-Human Identities (NHI) The **Non-Human Identities tab** surfaces service accounts, integrations, and AWS IAM principals — identities that have access to your data but aren't tied to a specific person's email address. ### What counts as a Non-Human Identity? NHIs fall into two groups: * **Registered identities** — service accounts and integrations that your team registers manually via the **Organization Identity** page in Settings. Once registered, an identity moves out of the human identities list and appears in the NHI tab instead. * **AWS IAM principals** — IAM roles and users with access to your AWS data. Available as a premium add-on — see below. ### What you can see for each NHI For each NHI, the tab shows: * **Display name / identifier** — how the identity is identified * **Type** — Role, User, or Service * **Max sensitivity** — the highest sensitivity level of any resource this identity can access * **Resource count** — the number of resources in scope Clicking an NHI opens a detail page with its full data resources table. ### Registering a Non-Human Identity To register a service account or integration: 1. Go to **Settings** in the left-hand navigation 2. Open **Organization Identity** page and select the **Non-Human Identities** tab 3. Click **Register** and enter the identity's email address or identifier 4. Select the appropriate subtype (Service Account, Bot, Integration, Shared Mailbox) 5. Save — the identity will appear in the NHI tab and be excluded from the human identities list > Reach out to your Technical Account Manager to help identify existing NHIs within your account! ## AWS IAM Identity Coverage > AWS IAM Identity Coverage is available as a premium add-on. To learn more or get it enabled for your environment, reach out to your Technical Account Manager. Teleskope can surface AWS IAM roles and users alongside your SaaS identities, giving you a unified view of who — and what — has access to your sensitive data across both cloud infrastructure and SaaS applications. With AWS IAM coverage enabled, the Non-Human Identities tab will include your AWS principals, showing: * **IAM roles and users** with access to your AWS data sources (e.g. S3) * **Max sensitivity** — the highest sensitivity level of any resource the principal can reach * **Resource count** — the number of AWS resources in scope AWS IAM principals are identified by ARN and appear separately from email-keyed identities, since they aren't tied to a specific person without an AWS Organizations or Identity Center connection. *** ## The Domains List The Domains list groups human identities by email domain, giving you a view of access by organization or domain rather than by individual user. This is particularly useful for understanding the scope of external or contractor access. For each domain you can see the number of identities associated with it and the count of resources those identities can access. Clicking a domain opens a **Domain Detail** page showing the individual identities within that domain and their access. *** ## Things to Know **Connector coverage** Identity View surfaces access data from Google Drive and SharePoint. Not all connectors may be enabled for your environment — check with your admin or Customer Engineer to confirm which sources are in scope for your organization. **Data freshness** Identity View reflects access data as of the last connector sync. If a permission was recently granted or revoked, it may not appear immediately. For questions about when data was last refreshed, reach out to your Customer Engineer. **Role-based access** Identity View requires the Identities role permission (Settings → Roles) and must be enabled for your environment. If you don't see Identities in your navigation, check with your admin, or reach out to your Customer Engineer to confirm it's enabled. *** ## Feedback Identity View is new and actively improving. If you run into unexpected results, have suggestions, or want to share what's working well, please reach out to your Technical Account Manager.