Global Filters

Apply consistent filtering across all workspace widgets for unified cross-functional data analysis

Overview

Global Filters let you apply one set of criteria across all compatible widgets in a workspace, so you do not need to filter each widget separately.

How it fits together: org admins define organization-level fields, app admins map those fields to fields in each app, and people using a workspace choose filter values from the global filter bar.

Prerequisites

• Org Admin access to create organization-level field definitions
• App Admin access for each app you want included in global filtering
• Agreement on which dimensions (for example company, region, or date range) should be shared across apps

---

Organization-level field definitions

Org admins create the global field definitions that other apps map to.

To open Organization Fields: Organization Settings > Organization Fields (under Platform)

Create and manage fields

1. Click Add Field.
2. Enter a Field Name using clear, organization-wide terminology.
3. Add a Description that explains what the field represents and how teams should use it.
4. Select the Type (Text, Number, Date, Dropdown, or other supported type).
5. Click Create to save.

The Organization Fields table lists each field’s name, type, description, and how many apps have mapped it. Use the search bar to find fields by name, description, or app.

To edit a field, click the Edit icon on the row, change the name or description, and click Apply.

Choose field types carefully. Changing a type after apps have created mappings can cause compatibility issues.

Naming fields

Use names that everyone in the organization will recognize, for example Company, Region, Date Range, Fiscal Quarter, Status, Department, Product Category.

Avoid ambiguous or internal codes such as Acct, DT, Stat, or Dept_CD—spell out the meaning others expect.

Before adding many fields, list the common dimensions your org needs (for example company, region, date range, status) and align types (for example Dropdown vs Date) with how data is stored in your apps.

---

App-level field mappings

App admins connect each organization field to a field in their app.

To open Field Mapping: In the app, under Configuration, click Field Mapping.

The page lists organization fields; use the dropdown beside each to choose the matching app field. If the app field type does not match the organization field type, an error icon indicates the problem. Use the search bar to find a mapping, and pick a different app field from the dropdown to change an existing mapping.

Organization field	Example app field (Sales)	Example app field (Support)
Company	Account_Name	Customer
Region	Sales_Territory	Support_Region
Status	Deal_Stage	Ticket_Status
Date Range	Close_Date	Created_Date

A mismatch often means the organization field is one type (for example Date) while the mapped app field is another (for example Text). Filtering may not behave correctly until types align.

After you save mappings, open a workspace that includes widgets from your app, set a global filter for a mapped field, and confirm the widgets update as expected. Try more than one value to verify behavior.

---

Using global filters

The global filter bar appears at the top of workspaces. It shows a control for each configured dimension (for example Company or Region).

1. Choose values for one or more dimensions. Within a single dimension you can often select multiple values (multi-select).
2. Filters combine with AND logic: records must satisfy all selected dimensions.
3. When you change a filter, compatible widgets refresh to match.

Widgets that do not have a mapping for a given dimension are unchanged when you set that filter.

To clear filters, remove individual criteria with the X on each pill, or use Clear All to reset everything.

---

Troubleshooting

Filter not working

What you see: Applying a global filter does not change widget data.

What to check:

1. The app has a field mapping for that filter dimension.
2. Field Mapping shows no type mismatch for that mapping.
3. The widget’s data actually uses the mapped field.
4. You have permission to see the records you expect after filtering.

Type mismatch

What you see: An error icon next to a mapping in Field Mapping.

What to do:

1. Compare the organization field type with the app field type.
2. Map to a different app field with a compatible type, or ask an org admin whether the organization field type should change.

Missing filter in workspace

What you see: A dimension you expect does not appear in the filter bar.

What to check:

1. An org admin created the organization field.
2. Apps used in that workspace have mapped that field.
3. If the field still does not appear, ask an org admin to confirm the field exists and that your apps are mapped.

---

Related Features

Filtering Fundamentals

Learn about basic filtering concepts and operators

Analytics

Create dashboards that work with global filters

Tables

Understand how data sources connect to global filtering

Roles & Permissions

Configure admin access for field mapping configuration