 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

πŸ‘―β€β™€οΈ On-Call Shadowing

πŸ”Œ Generic Webhook Alert Source

πŸ”’ Lock Individual Workflows

πŸ¦β€β¬› Round Robin Escalation Policies

🚨 Alert Sources

πŸ”” Configurable On-Call Shift Reminders

πŸͺ„ Dynamic Forms

πŸ” Granular Role-Based Access Control Settings for On-Call

βœ‰οΈ 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