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

๐Ÿคณ View Shifts, Create Overrides, and Escalate Alerts from Rootly Mobile

๐Ÿ˜… Alert Urgency

๐Ÿšจ New Alert Sources: Azure, CloudWatch, and Google Cloud

โ˜Ž๏ธ Live Call Routing

๐Ÿค‘ On-Call Pay Calculator

๐Ÿ’“ Heartbeats: Continuous System Monitoring

๐Ÿšจ Alert Grouping

๐Ÿค“ Smart Defaults for Google Meet & Zoom

๐Ÿงผ Redesigned Incident Announcement & Update Slack Blocks

๐Ÿ’… New Navigation Bar and Configuration UI

๐Ÿฅธ Sync On-Call Schedules with Slack User Groups

๐Ÿ•ต๏ธโ€โ™€๏ธ /rootly lookup: Find and Filter Recent Incidents in Slack

๐Ÿ‘ฏโ€โ™€๏ธ 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