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

• Users must have the TEAM-DASHBOARDS:UPDATE permission to lock or unlock a dashboard.
• 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.
• For older dashboards without an assigned creator, any team member can lock them.
• If you want to edit a locked dashboard but lack the necessary permissions, you can duplicate a dashboard by selecting Make a copy from the 3-dot menu next to the dashboard name in the Dashboards 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. Set a default access level for everyone in your team, then override it for specific groups as needed.

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 settings panel.

Step 1. Open the resource settings

Navigate to the resource (for example, a Custom Dashboard). Open its settings from the settings icon or more actions menu, then scroll to the Access Policy section.

Step 2. Select an access mode

Use the Who can access this <resource> dropdown to pick a mode:

• Private — only you can view and edit the resource. No further configuration is needed; save your changes and you're done.
• Advanced — opens the full policy editor for target group rules, general access, and policy permissions. Continue with the steps that follow.

Step 3. Apply to target groups (optional)

In the Apply to target groups section, define per-group access:

1. Search for and select a group in the group field.
2. Select an access level from the action dropdown. Available options differ by resource type — for example, Read, No Access, or Manage for saved views.
3. Select Apply to commit the rule.
4. Repeat to add more rules. To remove a rule, select the remove icon next to it.

Step 4. Set general access

In General access, select the default access level for everyone on your team who isn't covered by a target group rule. Available options differ by resource type.

Step 5. Configure policy permissions (optional)

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

Step 6. Save your changes

Select Save to activate the policy. To restore the default 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 the mode to Private.
• Result: Only the policy owner has access (and safety net, high privilege users).

Team‑only

• Goal: Only the App A Devs group can read (and optionally manage).
• Steps:
  1. Set the mode to Advanced.
  2. Set General access to Dashboard: No Access.
  3. In Apply to target groups, add a rule: target App A Devs → Dashboard: Read (or Dashboard: Manage if needed). Select Apply.
• Result: Users in App A Devs can read or manage; others are denied.

Everyone, except group X

• Goal: Broad read access for all, except block the London group.
• Steps:
  1. Set the mode to Advanced.
  2. Set General access to Dashboard: Read.
  3. In Apply to target groups, add a rule: target London → Dashboard: No Access. Select Apply.
• Result: All users can read, except the London group.

Read‑only for all; Product‑Managers can manage

• Goal: Everyone can read; Product‑Managers can also manage.
• Steps:
  1. Set the mode to Advanced.
  2. Set General access to Dashboard: Read.
  3. In Apply to target groups, add a rule: target Product‑Managers → Dashboard: Manage. Select Apply.
• Result: All users can read; Product‑Managers can manage.

Sensitive dashboard visible only to SOC‑Analysts

• Goal: Keep it private to SOC‑Analysts.
• Steps:
  1. Set the mode to Advanced.
  2. Set General access to Dashboard: No Access.
  3. In Apply to target groups, add a rule: target SOC‑Analysts → Dashboard: Read (and Dashboard: Manage if needed). Select Apply.
• Result: Only SOC‑Analysts have access.

Next steps

Learn how to share dashboard content.