Back to Changelog
Back to Changelog

March 1, 2024

Others

📊 Dashboard Sharing Permissions

📊 Dashboard Sharing Permissions

📊 Dashboard Sharing Permissions

Controlling who can access your incident data is paramount, especially for large organizations. You might have dashboards which contain information only relevant to a specific team, or some you only want accessible to Executives, etc. With our Dashboard Sharing settings, this is no problem.

When you create a new dashboard, it will be private by default—meaning it will be only accessible by you unless you choose to share it using the Share button in the top right. From there, you can select whether you want to share it with your full team or specific individuals, and select their level of access to any of the options below:

Viewer: Can view the dashboard but can’t make any changes.
Editor: Can view the dashboard and add/remove/edit panels within it.
Manager: Can view the dashboard, edit its content, and update sharing settings.

There’s also an option to create a public link to view, which is useful for teams who want to share specific dashboards with their customers or other stakeholders outside of the organization.

🌝 New & Improved

🆕 Added new setting to allow users to not to be tagged in the initial Slack block following an incident role assignment. This will help quiet down the notifications to the assigned users. You can access this new setting by going to Account Settings > Notifications > When your user appears in the initial incident message mention your user (ex. @rootly_bot)
💅 Tutorial incidents is now unlocked for ALL users - even users without full incident permissions. New users can learn the basic Rootly operations by running the /rootly tutorial command in Slack.
💅 Cleaned up inconsistent symbols used to indicate users’ Slack connection statuses. Now, users that have their Slack accounts connected will see a green check mark in the Slack Connected column on the Organization Settings > Members page.
🐛 Fixed required field asterisk (*) display issue on New Incident forms on Slack
🐛 Fixed issue with individual retrospective steps not auto-assigning to the specified incident roles
🐛 Fixed auto format issue on the names entered for Incident Permissions Sets
🐛 Fixed color distortion on Incident Insights heatmap shown on the Dashboard page.

Previous post
Previous post
You are viewing the latest post

Custom Fields

Automatically Schedule Postmortem Reviews

Auto Create Incidents from Any Alert

Terraform Provider for Rootly

Get Support From Rootly in Slack

Bookmark Anything in Incident Slack Channel

Convert Existing Channels to Rootly Incidents

Incident Preview

Custom Role-Based Access Control (RBAC)

Subscribe to Incidents

Workflow Templates

Incident Variables and Snippets

Invite Responders to Incidents via Slack

Severity Descriptions

Reopening Incidents

SOC 2 Type II Certified

Trigger Workflows Anytime

Making Incident Creation a Breeze

Workflows 2.0

API and Infrastructure as Code Ready

Slack Enterprise Grid & Multi-Workspace Ready

Quick Start Shortcuts

Keep It Private (Incidents)

Measuring Incident Cost

Saying Hello to Rootly.com