Omnitable Named Views Sharing

Overview

Omnitable Named Views can be shared with the entire organization. Starting with the 2026.06 release, users with the appropriate permission can mark a view as Public, making it available to all users in the Org. Admins can also designate one Public view as the Org-wide default, so new users or users without a personal default automatically load a consistent starting configuration.

Main Features

Private and Public Visibility

When creating or editing a Named View, eligible users now see a visibility selector: Private (visible only to me) or Public (visible to all users in the org).

The visibility setting can be changed after a view is created. A Public view can be made Private, and vice versa, by its owner or an admin.

Users without the Create_Public_Views permission can still view and apply Public views; they just cannot create them or change their visibility.

Save As

Any user can save a copy of a Public view as their own Private view using the new Save As action.

This lets teams share a standard starting configuration while allowing individuals to personalize their own copy without affecting the shared original.

User Override

Users with the “Edit_All_Public_Views” permission can edit and save Named Views owned by other users e.g., to update a shared team view without requiring the original owner to be available.

Org-wide Default View

An admin can designate one Public Named View as the Org-wide default.

Any user who has not set a personal default view will automatically load this view when opening Omnitable.

If the designated default is deleted or its visibility is changed to Private, the system gracefully clears the assignment — no errors, no broken sessions. A new default can be set at any time.

Permissions Model

The table below summarizes what each user type can do:

Setup & Configuration

Assign Permission

In Salesforce Setup, assign the Create_Public_Views Custom Permission to any user profile that should be allowed to create or edit Public Named Views. Users without this permission can still view and use Public views, and can save their own copies via Save As. They just cannot create new Public views.

Existing Views

All existing Named Views are treated as Private after the upgrade. No data migration is required. Users will continue to see exactly what they saw before.

Set an Org-wide Default (Optional)

Any admin can designate one Public Named View as the Org-wide default for an Omnitable. Users who have not set a personal default will automatically load this view on new sessions.

To set an Org-wide default:

1. Locate the Public Named View record ID.

2. Go to Setup> Custom Metadata Types> Named Setting(BH4SF).

3. Select the Omnitable you want to edit.

4. Add defaultViewId": "#ID of the view" .

{
"objectName": "TR1__Application_V2__c",
"defaultFields": "TR1__ATSv2_Default_Candidate_FieldSet",
"contextFilterFieldName": "TR1__Job__c",
"defaultViewId": "#Record ID of the view"
}

Edge Case Behaviors

If the Org-wide default view is deleted or changed from Public to Private, the system automatically clears the default assignment. No error is shown to users — they simply load Omnitable without a pre-selected view until a new default is set. If a Named View was shared by a user who has been deactivated, the view will still be visible to users, but marked as created by "deactivated user" (instead of the user’s name) The default view does not take precedence over a locally pinned view set by the user.