Scoped Views

Scoped Views allow organizations to define persistent, reusable filters that control how cloud cost data is displayed to users. These views can represent business units, product lines, teams, environments, or any logical grouping built from cloud provider dimensions or Ternary Custom Labels.

Administrators can assign views at the organization level and control whether users can toggle those selections. Users can also create personal Scoped Views for their own analysis. Browser selections filter the displayed data; they do not by themselves establish a server-side access restriction.

Scoped Views support reusable reporting logic and segmentation of cost data across dashboards and reports.

Tutorial - Scoped Views for users with "Regular User" role

Tutorial - Scoped Views for users with "Owner" role (administrators)

How are Scoped Views created and assigned to users?

Organization-level Scoped Views are managed from the Admin section of the platform. To create a new organization-level Scoped View:

• Navigate to Admin.
• Open the Scoped Views section.
• Click Create Scoped View.
• Enter a clear and descriptive name that users will recognize.
• Define one or more filters using Ternary custom labels or native cloud billing dimensions.

All filters within a single Scoped View are evaluated using AND logic, meaning all defined conditions must be satisfied for data to be included.

How do I manage personal Scoped Views?

Open My Scoped Views in user settings to create and manage your personal views. Use search to locate a view and review its name, filter count and enabled state.

Current observed limitation: In Preview testing on October 28, 2026, creating a personal view with On by default enabled returned a creation error and no saved view. Creating it with this option off, then opening Edit and enabling it, succeeded. This workaround applies to the observed limitation, including personal copies and views saved from current filters; it is not a general requirement for personal Scoped Views.

Create a personal view

1. Select Create Scoped View and enter a descriptive name.
2. Use Add Dataset and choose FOCUS, Kube Container or Kube Nodes. Choose each filter's dimension and operator, then supply its values. Choose Equals, Does not equal, Contains, Does not contain, Is set or Is not set as needed. For value-taking operators, use the value picker; Contains can store a list of selected values. Is set does not need a value.
3. Select suggested values, then confirm the selected values with Apply. If you change a dimension, enter its values again because changing the dimension clears them.
4. Submit the form and wait for the success confirmation. The new personal view appears in the refreshed list.

Edit, copy or delete a view

For a personal view you created, choose Edit, change its name or filters, and save the changes. Review the form before submitting your changes. Updating a view that is active for you can also update your current filters.

Choose Make Copy to start a new personal view with the source filters and a copy suffix in its name. Review the copied filters and name before submitting.

Choose Delete to remove a personal view you own. Review the confirmation before proceeding: deletion is permanent. A successful deletion refreshes the list and adjusts your current filters if that view was active.

Turning On by default off for your view removes it from your active selection. Check your current filters after changing or deleting an active view.

How do I save my current filters as a Scoped View?

Open the Scoped Views selector to reuse filters you have already assembled. Select Create Scoped View to open Save as Scoped View.

1. Enter a descriptive name.
2. Under Include, choose the content to save:
   • Filters only copies your custom filters.
   • Scoped views only copies the definitions from the selected Scoped Views.
   • Scoped views and filters combines both.
3. Review the included content. The chosen option must contain filters or selected views, and included custom filters must have valid fields.
4. Keep Personal, the default, for your own reuse. See the current observed limitation when enabling a new personal view by default.
5. Select Submit and wait for the success confirmation. The new view appears in the available Scoped Views; the drawer closing alone does not confirm a successful save.

What is preserved when I save?

The new view stores copied filter definitions, rather than links to the selected source views. Later edits to a source view do not update the saved copy.

Saving combines filters that have the same dataset and dimension, removes duplicate values and retains the first matching filter's operator. It does not preserve arbitrary OR groupings between source views. If you save a combination of views with different conditions, review the new definition before relying on it to reproduce the original results. For example, two source views with different operators for the same dimension are not retained as two independent conditions.

Saving a personal view is separate from applying it to the current analysis.

How can Scoped Views be applied to users?

When assigning a Scoped View, four application modes are available. Each controls how the view behaves for the assigned user.

• Available For: Users will see the Scoped View listed under Organization Level Scoped Views on supported pages. It is not automatically applied at login. Users can enable or disable it at their discretion.
• Enforced For: The view is selected with locked controls in the browser filter dialog. Its filters join the same selected-view group as other selected organizational and personal views.
• Enabled by Default For: The Scoped View is automatically applied at login. Unlike Enforced, users can toggle it on or off during their session.
• Strictly Enabled For: Users can choose among their strictly enabled views, but at least one must remain active in the browser filter dialog. To mute the last active strictly enabled view, enable another strictly enabled view first.

In browser filtering, conditions within each selected view combine with AND, while separate selected views combine with OR. Custom filters combine with AND on top of that group. Enforced views therefore do not create an AND intersection across selected views; a selected personal view also joins the OR group. This describes how browser filters combine, not a universal access restriction across reports and emailed results.

Users are assigned through the dropdown selector in each section. Once assigned to one mode, a user will not appear in the other assignment lists.

A summary table at the bottom of the page displays all current user assignments. Users can be removed from a list using the remove icon.

Your current browser selections are separate from saved Scoped View assignments. Apply updates current selections; Cancel restores the URL selections. Clear Filters removes voluntary selections and custom filters while retaining selected Enforced and Strictly Enabled views. Muting a view does not change its saved assignment.

What additional assignment options are available?

Two global assignment options are available when configuring a Scoped View:

Apply to New Users adds the configured organizational Scoped View assignment when organization access is granted, only if the user has no existing assignment. It does not overwrite existing assignments; personal views and SSO group assignment follow separate paths.

The form supports Available, Enabled by Default and Enforced defaults. Current limitation (reviewed October 29, 2026): The displayed Strictly Enabled switch does not currently save a new strict default; do not rely on it to configure that default.

Apply to All Users: Applies the Scoped View to all existing users using the selected mode.

How does the Scoped View indicator behave?

After a Scoped View is created and assigned, its status is visually indicated within the interface. Here are the relevant examples:

1. Available For:

2. Enhanced For:

3. Enabled by Default For:

4. Strictly Enabled For:

How does the Scoped View indicator behave?

After a Scoped View is created and assigned, its status is visually indicated within the interface:

• Grey: No Scoped View applied
• Blue: Organization or personal Scoped View applied
• Red: Scoped View available but disabled or muted

These indicators help users quickly understand whether filters are currently active.

Where can Scoped Views be applied?

Scoped Views can currently be applied to the following areas of the platform:

• Home
• Reporting Engine Dashboards
• Reporting Engine Reports
• Cost Reports

Filters apply only to the dataset they define; billing filters do not automatically scope Kubernetes usage.

What are the use cases of Ternary Scoped Views?

Use Case 1: Creating flexible aggregations of projects, services, or labels

Scoped Views allow flexible include and exclude logic across multiple dimensions. For example, the below mentioned view:

• Excludes a cloud label that represents shared services
• Includes resources where the label cluster contains bigco
• Includes a defined list of specific projects

After entering a name for the new Scoped View, the process consists of defining the criteria that determine what data is included. It is possible to create combinations that result in no matching data. In those cases, reports and dashboards will display a “No Data to Display” message when the view is applied.

Use Case 2: Reusing generic dashboards and reports

Scoped Views make it possible to maintain a single generic dashboard and dynamically tailor it based on the logged in user. For example, DevOps leaders may each need visibility into the projects they control. Instead of rebuilding dashboards for each team:

1. Build generic report templates without applying team specific filters. Examples include:
   Compute Costs by Family
   Spending by Category Before Credits
2. Create Scoped Views that represent each team’s projects or cost dimensions.
3. Ensure the Scoped View and report grouping are logically aligned.
   A good example: Cost by Project combined with a Scoped View of Projects for Team A.
   A poor example: Cost by Project combined with a Scoped View of Services with Credits, since credits are not typically applied at the individual project level.

Example of a Default Dashboard with no Scoped View Applied:

When a user applies a Scoped View using the Scoped Views selector, the same generic dashboard dynamically reflects only the data relevant to that user’s scope.

SSO Driven Assignment of Scoped Views

SSO-driven group assignment allows Scoped Views to be automatically applied to users based on group membership defined in an external identity provider. When a user accesses Ternary through SSO, the platform evaluates group information passed in the IdP token and applies the corresponding Scoped Views without manual intervention.

SSO group changes are processed when a subsequent sign-in supplies a group set different from the user's stored groups. Changing membership in the identity provider does not immediately update an existing Ternary session. Check the resulting assignments; successful sign-in alone does not confirm that every Scoped View update succeeded.

More details on prerequisites and configuration can be accessed here.