# Why Two Users Might See Different Data in Omni Dashboards

**URL:** <https://community.omni.co/t/why-two-users-might-see-different-data-in-omni-dashboards/419>\
**Category:** Workbooks\
**Tags:** dashboards\
**Created:** [November 10, 2025, 11:46pm UTC](https://community.omni.co/t/why-two-users-might-see-different-data-in-omni-dashboards/419 "2025-11-10T23:46:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![James](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@James](https://community.omni.co/u/James)\
**Post date:** [November 10, 2025, 11:46pm UTC](https://community.omni.co/t/why-two-users-might-see-different-data-in-omni-dashboards/419/1 "2025-11-10T23:46:32Z")

</div>

When two users view the same dashboard but see different results, there may be differences in filters, cache, access controls, or time zone configurations. This article walks through each factor to help you diagnose and resolve discrepancies.

* * *

## Filters

Dashboard filters are the first thing to check.  
If filters are set differently between users, they’ll naturally get different query results.

Confirm that all filter values match exactly for both users.

* * *

## Cache

Caching may lead to temporary differences in results if one user is served cached data and another runs a fresh query.

- **Run without cache:** Try refreshing the dashboard with cache disabled to ensure you’re pulling the latest data from the database.  
See the [Query Cache documentation](https://docs.omni.co/docs/querying-and-sql/caching#query-cache).

- **Filter suggestion cache:**  
Filter dropdowns use a _suggestion cache_ that lasts 30 days by default. New values may not appear immediately, which can cause users to select different filters or think certain filters are missing.  
To make suggestion caches respect your dashboard’s cache policy, enable the [`filter_suggestions_must_obey_policy`](https://docs.omni.co/docs/modeling/model-files#filter_suggestions_must_obey_policy) parameter at the model level.

* * *

## Access

### Attributes

Access filters and grants may lead to data differences when users don’t share the same `user_attributes`.

- **Access filters** — These apply row-level filters

- **Access grants** — These can restrict access to specific views or fields.

Check the `user_attributes` defined for both users and review whether any `access_grants` or `access_filters` are active in the views, topics, or models powering the dashboard.

> **[Controlling data access | Omni Analytics Documentation](https://docs.omni.co/docs/modeling/manage-develop/data-access-control)**
>
> Using a combination of user attributes and modeling parameters, you can control how data is accessed in your Omni models. To gain access to data - such as a topic, table, field, or row - users must have a user attribute with the required value.

* * *

### Permissions

Even if both users can open the same dashboard, connection roles and database routing may differ:

- **Connection roles:**  
Roles such as _Restricted Querier_ vs. _Querier_ can control who can execute queries. See [Access Warnings](https://docs.omni.co/docs/finding-content/content-sharing#access-warnings) for more details.

- **Dynamic environments:**  
If your setup routes users to different databases, schemas, or roles via `user_attributes`, or the dashboard uses a `warehouse_override`, the users may be querying different backends entirely. [Dynamically switching database environments | Omni Analytics Documentation](https://docs.omni.co/docs/connections/manage/dynamic-database-environments)

Confirm both users are using the same database environment, schema, and warehouse.

* * *

## Time Zones

Differences in time zone handling can shift date boundaries, affecting counts and aggregations.

Omni supports user-specific time zones if enabled at the connection level and passed through the `omni_user_timezone` attribute.

Check that both users’ effective time zones are the same.  
If the org or connection is configured with “Do not convert,” date fields will remain in database time — which can explain discrepancies in day-level totals.

> **[Database timezone settings | Omni Analytics Documentation](https://docs.omni.co/docs/connections/manage/timezones)**
>
> Omni can convert time-based data to different timezones, performing the conversion when it generates SQL for a query. The underlying data is not changed. Instead, Omni converts the query results using the connection's timezone settings.

* * *

### Summary

When users see different dashboard results, check the following in order:

1. **Filters** — Confirm identical filter values.

2. **Cache** — Refresh with cache disabled and verify suggestion cache behavior.

3. **Access** — Compare `user_attributes`, `access_grants`, and connection roles.

4. **Time Zones** — Align time zone settings across users.

Consistent settings across these four areas ensure your team sees the same, accurate and expected data.