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 select Share dashboard URL in the dashboard's more actions menu, and a slug has been set, the slug replaces the dashboard ID in the URL path following /dashboards/. For example: https://company-team-1.coralogix.com/#/dashboards/s/my-dashboard-slug.

To learn more about sharing dashboards, widgets, and sections, see Share Dashboard Content.

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 on-hover more actions menu in the dashboard list.

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 from the resource's Access policy section.

Step 1. Set general access

General access sets the default access level for everyone in your team. Select an access level from the dropdown — available options differ by resource type.

Step 2. Add target group rules (optional)

Override the default for specific groups:

1. In the Add groups to define a rule field, search for and select one or more groups.
2. Set the access level for the group using the dropdown.
3. To add another rule, select + Add.
4. To remove a rule, select the remove icon next to it.

Step 3. Configure policy access (optional)

To control who can view or edit the policy itself, toggle on Show advanced. This reveals a Policy column next to each rule row. Set the policy access level for each row as needed.

Step 4. Save your changes

Select Save to activate the policy. To restore the default policy configuration, select Reset.

Learn more about policy-based access control.

Policy-configuration examples

Only me (Private)

• Goal: No one else can view, manage, or take any other action.
• Steps:
  1. Set General access to Dashboard: No access.
  2. Add no group rules.
• Result: Only the policy owner has access (and safety net, high privilege users).

Team‑only

• Goal: Only the App A Devs group can view (and optionally edit).
• Steps:
  1. Set General access to Dashboard: No access.
  2. Add a rule: target App A Devs → Dashboard: View (or Dashboard: Edit if needed).
• Result: Users in App A Devs can view or edit; others are denied.

Everyone, except group X

• Goal: Broad view access for all, except block the London group.
• Steps:
  1. Set General access to Dashboard: View.
  2. Add a rule: target London → Dashboard: No access.
• Result: All users can view, except the London group.

View‑only for all; Product‑Managers can edit

• Goal: Everyone can view; Product‑Managers can also edit.
• Steps:
  1. Set General access to Dashboard: View.
  2. Add a rule: target Product‑Managers → Dashboard: Edit.
• Result: All users can view; Product‑Managers can edit.

Sensitive dashboard visible only to SOC‑Analysts

• Goal: Keep it private to SOC‑Analysts.
• Steps:
  1. Set General access to Dashboard: No access.
  2. Add a rule: target SOC‑Analysts → Dashboard: View (and Dashboard: Edit if needed).
• Result: Only SOC‑Analysts have access.

Folder policies

Apply a policy to a folder to cascade it automatically to all dashboards and subfolders inside. This lets you manage access for many dashboards at once without configuring each one individually.

Inheritance behavior:

• All dashboards and subfolders inside a folder inherit the folder's policy.
• Dashboards with their own access policy are not affected — dashboard-level policies take precedence.
• The more specific level always wins: dashboard policy overrides subfolder policy, which overrides folder policy.

Drag-and-drop behavior:

• Moving a dashboard or subfolder into a folder applies that folder's policy automatically.
• Moving a dashboard or subfolder out of a folder removes the folder's policy. If moved to another folder, the new folder's policy applies. If moved to the root level, the default general access policy applies.

Set folder policies when creating or editing a folder from the DASHBOARDS LIST more actions menu. Policies are also available via API for IaC workflows.