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

✉️ Emails as an On-Call Alert Source

🗓️ View Multiple On-Call Schedules Together

🤝 Partial Shift Overrides in Rootly On-Call

🏗️ Terraform + API Support for Rootly On-Call

🦉 Rootly x Thena Integration

🎬 New Full Platform Tour on Rootly.com

🔦 Drop-down Search in Escalation Policy Builder

🦊 GitLab Integration

Update Custom Incident Fields Using Workflows

🤖 Ask Rootly AI (+ More New AI Features!)

Rootly AI Editor: Fix Typos, Grammatical Errors, and Wordy Text Instantly

📊 Dashboard Sharing Permissions

✍️ Customize Your Wordbank for Automatic Incident Title Generation

🧠 Smart Defaults for Jira

🔌 The Rootly Plugin for Zendesk

🪄 Rootly Retrospectives

⚡ Command Palette: Lightning Fast Navigation with a Single Keyboard Command

Rootly Terraformer: Seamlessly Bring Workflows From Rootly’s UI to Terraform

Smart Defaults for Slack Configuration

Rootly Rewind: Celebrating 2023 With Our Amazing Customers!

Search and Filter Available Actions for Workflows

Incident Timeline Comments: Add Context and Move from Conversation to Action Seamlessly

Introducing: Rootly x ClickUp! Our New Integration for Seamless Collaboration and Task-Tracking

The New and Improved Home Dashboard

Guided Onboarding Flow for New Rootly Users