Manage Dashboard Settings

Overview

The settings panel gives you centralized access to key dashboard options. You can rename your dashboard, edit its description, assign a slug, lock it from changes, and choose where it appears in your dashboards list-all in one unified place. To learn more about creating and using dashboards, see the Custom Dashboards overview.

You can access the settings panel from:

• The more actions menu in the upper-right corner of the dashboard.
• The more actions menu that appears when you hover over a dashboard in the DASHBOARDS LIST on the left.

The panel includes two sections:

• General settings: System-level options that affect the dashboard itself, such as setting the title and description.
• User preferences: Personal settings that affect how you interact with the dashboard.

Saving behavior

To save dashboard settings like title, description, or slug, you must click Apply, then Save in the main dashboard view. Clicking Apply alone won’t save these changes permanently.

User preferences, however, are saved to your dashboard immediately when you click Apply. No further action is needed.

User preferences are not available when creating a new dashboard. You’ll need to save the dashboard first to access them.

Title

You can rename your dashboard at any time. Use a clear and descriptive name that makes it easy to locate in the DASHBOARDS LIST. New dashboards are named New Dashboard by default. To rename it, click on the title and enter a new name.

Dashboards saved from Visual Explorer are automatically titled Visual Explorer, followed by the date and time of the save-for example, Visual Explorer - 15/07/25 09:37:09.

Description

The description provides a short summary of the dashboard's purpose or the insights it provides. It appears in the dashboard tooltip to help viewers quickly understand the context.

Folder

Assign the dashboard to a folder to organize it in the DASHBOARDS LIST. Folders make it easier to group dashboards by team, environment, use case, or ownership. You can change the folder assignment at any time.

Dashboard slug

A slug is a custom URL-safe name that you can assign to your dashboard. This is useful when:

• Referencing your dashboard programmatically.
• Sharing your dashboard as a link.
• Building custom actions that target a specific dashboard.
• Navigating between duplicate dashboards across multiple teams—by using the same slug and simply replacing the team name in the URL.

If you copy the dashboard URL with the Copy URL action in the more actions menu, and a slug has been set, the slug replaces the dashboard ID in the browser URL path following /dashboards/. For example: https://company-team-1.coralogix.com/#/dashboards/s/my-dashboard-slug.

Slug requirements

• Slugs must be unique within your team.
• Only lowercase letters, numbers, hyphens (-) and underscores (_) are supported.
• Spaces and special characters are not supported.
• Slugs can’t begin or end with hyphens (-) or underscores (_).

System metadata

A tooltip next to the dashboard title displays metadata including, the dashboard's description, creation date, and last modified date.

The tooltip automatically updates when a dashboard is changed.

A dashboard can be created or modified either by a user through the Coralogix UI or via external API actions. If a team-level API key is used, the key name will be shown as the creator or modifier in the dashboard tooltip.

User preferences

Star dashboard

Mark the dashboard as a favorite to pin it to the top of your dashboard list.

Set as default dashboard

Make this your home dashboard, shown by default when you open Custom Dashboards.

Lock dashboard

Locking a dashboard prevents unauthorized modifications while preserving its current state.

Locking prevents others from making changes to the dashboard layout or its widgets. When a dashboard is locked, a padlock icon appears next to its title. To unlock it, return to the settings panel and toggle Lock dashboard.

Lock behavior

• Only the dashboard creator can lock or unlock it.
• Locking records the user who performed the action in the dashboard metadata.
• If a dashboard was created using a team-level API key, any team member can lock it.
• If you want to edit a locked dashboard but lack the necessary permissions, you can duplicate a dashboard by clicking Make a copy in the dashboard more actions menu.

Locking dashboards helps protect critical dashboards from accidental changes while still allowing team members to duplicate them when edits are needed.

Access policies

Access policies let you specify exactly who can view or manage your dashboard. They work by defining a default rule that applies to everyone in your account and optional exception rules for specific groups. Together, these rules give you precise control over dashboard visibility and permitted actions.

Use it to:

• Keep a dashboard visible to only you
• Allow team-only access for a specific group
• Grant access to everyone except specific groups

Create a policy

Follow these steps on the entity’s policy page.

1. Turn on policy (empty state)

Enable policy creation by toggling the switch. This turns the policy on for a specific entity (Access mode becomes Restricted).

2. Set the default rule (baseline)

The default rule sets the baseline for all users who have the relevant permissions for this entity type. You can override this baseline for specific groups using exception rules.

Choose the allowed actions for both the resource and the policy itself.

Available options include:

• Resource actions: Control what users can do with the entity (e.g, Read to view a dashboard, or Update to edit it).
• Policy actions (Read Current Access Policy and Update Current Access Policy): Control who can view or edit the policy configuration itself.

Select None or Enabled:

• None: No one can take actions on the entity except the policy creator.
• Enabled: Choose the baseline actions to allow (for example, read). Available actions differ by entity type. Selecting all permitted actions effectively mirrors the RBAC behavior.

3. Add exception rules

Use exception rules to adjust access for specific groups relative to the default.

• If the default is Enabled → Read, you can add an exception to grant a group manage.
• If the default is None, you can add an exception to grant a group read and/or manage.
• To block a specific group when the default allows access, add an exception for that group with allowed actions set to None.

Select a target group and specify the allowed actions for that group. Add multiple rules as needed.

Learn more about policy-based access control.

Use cases

Restricted access to everyone

To keep the dashboard private, enable the policy and set Allowed actions to None.

Permit access to a single group

To allow access only to a single group of users, enable the policy and set Allowed actions to None. Then in the Exception rules, select the Target group (e.g., Developers) with read and manage access to your dashboard.