Entities

The Entities page provides a structured, tabular view of every node in the Context Graph. While the Graph Explorer is ideal for visual discovery, the Entities page is optimized for searching, filtering, sorting, and inspecting detailed properties of individual entities. It serves as the most direct way to browse and analyze the full dataset that Kubiya has ingested from all connected integrations.

​

Prerequisites

To see meaningful content in the Entities page:

• At least one data source or integration must have ingested entities
• Entity types (labels) must be available in the graph
• Ingestion must have completed successfully so that entity metadata is populated

If no sources are connected or ingestion has not begun, the table will remain empty.

​

Page Layout and Components

The Entities page includes:

1. Search bar: free-text filtering across names and properties
2. Filters: integrations and entity types
3. Entities table: tabular list with details and actions
4. Pagination: navigate through large datasets
5. Entity Details Panel: full detail view when selecting “View”

Each section helps users navigate and inspect the dataset efficiently.

​

Global Search

At the top of the page, the search bar “Search entities by name, ID, or properties…” allows filtering across all fields indexed for each entity. You can search using:

• Partial names
• Unique IDs
• Cloud resource identifiers
• Integration-specific properties
• Custom ingestion fields

The table updates instantly to reflect the search results

​

Filters

​

Integration Filters

This filter shows all integrations contributing data to the graph, such as:

• AWS
• CSV
• Custom

Selecting one limits the entity list to nodes originating from that integration. Users can combine integration filters with entity type filters for focused analysis.

​

Entity Type (Label) Filters

Below integrations is a full list of label types present in the graph. Each label corresponds to an entity type (for example: accounts, IAM objects, network components, storage resources, custom ingested items, and more). Selecting one or more labels filters the table to show only entities of those types. Because the label list can be long, it is:

• Scrollable
• Color-coded
• Fully selectable
• Clearly grouped under “Entity Types (Labels)”

Filters remain active until manually cleared.

​

Entities Table

The table displays all entities matching the current search + filter criteria. Columns include:

​

Name

The entity’s primary display name. This may be a human-readable identifier, a username, a resource name, or any unique label derived from ingestion. Beneath the name, the entity’s internal graph ID is shown.

​

Type

The type of the entity as interpreted by Kubiya. This corresponds to the specific label applied: such as AWSPrincipal, EC2Instance, DNSRecord, CustomObject, or any other supported type.

​

Integration

Shows which integration the entity originated from. This helps differentiate between cloud data, CSV uploads, or custom ingestion streams.

​

Labels

The full set of labels attached to the entity. Entities often have multiple labels that describe their type, classification, or integration metadata. These labels match what appears in Graph Explorer and are consistent across the entire Context Graph.

​

Last Updated

Timestamp showing the last time the entity was refreshed by ingestion. This helps verify recency and detect outdated or stale data.

​

Actions (View)

Clicking View opens the full detail panel for the selected entity on the right side of the page.

​

Entity Details Panel

Selecting View brings up a detailed panel, mirroring what appears when clicking a node in Graph Explorer but with more context and complete information. The panel includes:

​

Labels

All labels applied to the entity, such as identity, policy, resource, or integration-specific categories.

​

Metadata

Includes:

• Last Updated
• First Seen
• Node ID

These fields help track ingestion history and trace changes over time.

​

Properties

A structured list of all properties ingested for the entity. Depending on the type, properties may include:

• Name
• Path
• Created Date
• ARN
• UserId
• Internal fields from AWS, CSV, or custom sources

Properties appear exactly as provided by the data source, making this panel the most reliable place to inspect raw attributes.

​

Relationships

Every relationship connected to the entity is shown here, grouped and labeled clearly. For each relationship, the panel displays:

• Relationship type (e.g., RESOURCE, POLICY, AWS_ACCESS_KEY)
• Direction (incoming or outgoing)
• Target node name
• Target node type

Each relationship card includes a link icon that opens the related node’s detail page. This section helps users trace connections such as:

• IAM principals linked to policies
• Roles associated with access keys
• Resources connected to accounts
• Custom entities linked via ingestion relationships

This is the most precise way to understand how an entity fits into the wider graph.

​

Pagination

At the bottom of the table:

• Users can choose how many entities to display per page (e.g., 50)
• Navigation arrows allow moving between pages
• Total entity count is displayed clearly (e.g., “3,300 entities”)

This makes it feasible to browse very large datasets.

​

How the Entities Page Helps

The Entities page is used to:

• Inspect specific resources, identities, or objects in detail
• Validate ingestion outputs from each data source
• See exact metadata and timestamps for each entity
• Review relationship connections to understand graph topology
• Debug unexpected or missing resources
• Locate entities before writing Cypher queries
• Navigate to deeper investigation using the entity detail panel

It is the most structured, searchable, and complete view of all nodes in the Context Graph.

​

What’s Next

Once you’ve explored entities in the table, the following pages allow deeper analysis:

• Queries Write and execute Cypher queries to filter, join, and analyze graph data programmatically.
• Data Sources View all integrated systems, ingestion counts, and connect new sources to expand the graph.

These pages work together to help you explore your organizational data from every angle.