Users as a Resource

Euno recognizes users as native resources within the data model, treating them as first-class citizens alongside tables, dashboards, dbt models, and other data assets. This enables comprehensive tracking of user relationships, and dependencies across your entire data stack.

By modeling users as resources, you can:

• Query relationships between users and data assets

• Perform impact analysis involving users

• Understand who depends on what data and who produces it

Resource Types

User Account (user)

Represents an individual user in your organization.

URI Format:

user.<EMAIL_ADDRESS>

The email address is normalized by replacing @ with _at_ and converting to lowercase.

Examples:

• user.john_at_example.com

• user.data.engineer_at_company.com

User Group (user_group)

Represents a group of users, typically synchronized from identity providers like Microsoft Entra ID or Google Workspace.

URI Format:

user_group.<GROUP_ID>

The group ID is typically a unique identifier from the identity provider (e.g., Microsoft Entra ID group ID).

Examples:

• user_group.cf9fa9ef-3315-459c-893f-a44ec0e26ac1

• user_group.4f5024be-9361-4dd9-8996-14c1f06a5dc3

Properties

User Account Properties

Property	Description
name	Display name of the user
email_address	Email address of the user (primary identifier)
label	Display label for the user
subtype	Source of the user (e.g., google_workspace, entra_id)

User Group Properties

Property	Description
name	Display name of the group
subtype	Source of the group (e.g., google_workspace, entra_id)
native_id	Native identifier from the source system
created_at	Timestamp when the group was created
members	List of user and group members belonging to this group

Relationships

Users participate in the same relationship model as other resources in Euno. For a complete reference on relationship types, see Relationships.

Membership Relationships

Users can belong to groups, and groups can contain nested groups.

user ──[is member of]──> user_group
user_group ──[is member of]──> user_group (nested groups)

Usage Relationships

Track which resources users access and consume.

user ──[is user of]──> dashboard, report, table

Querying Users with EQL

Find All Users

type = "user"

Find All User Groups

type = "user_group"

Find Users by Email Domain

type = "user" AND email_address ~ "@company.com"

Find Groups a User Belongs To

type = "user_group" AND has member(uri = "user.john_at_example.com")

Find All Members of a Group

type = "user" AND has group(name = "Data Engineering Team")

Find Dashboards Used by a User

type = "looker_dashboard" AND is used by(uri = "user.john_at_example.com")

Find Tables Consumed by Users in a Specific Group

type = "table" AND is used by(type = "user" AND has group(name = "Analytics Team"))

Use Cases

Impact Analysis

Determine which users will be affected by changes to a specific resource:

type = "user" AND is user of(uri = "snowflake.db.schema.critical_table")

Access Pattern Analysis

Understand how users interact with data assets by querying user-resource relationships.

Team Dependencies

Analyze which data assets a team depends on:

is used by(has group(name = "Finance Team"))

Enabling User Observation

User observation is enabled through supported BI integrations. Currently, the following integrations support user observation:

Integration	User Types Discovered	Setup
Looker	user, user_group	Enable "Observe users" and/or "Observe groups" in advanced settings
Power BI	user, user_group	Enable "Observe users" and/or "Observe groups" in advanced settings
Tableau	user	Automatic with standard integration

Related Topics

• Relationships - Complete relationship reference

• Universal Resource Identifier (URI) - URI format reference

• EQL Query Language - Query language documentation