๎‚ 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

Customize Your Incident Overview Banner in Slack

Improved Confluence Retrospective Templates

Workflows Can Now Automatically Update Previously Posted Slack Messages

Automate Component Status Updates on Statuspage.io

Rootly Joins the Vendr+ Marketplace

Assign Multiple Users to the Same Incident Role

Incident Triage: Investigate Potential Incidents Faster

Rootly + Fivetran Data Connector Integration

Less Noise, More Flexibility: New Slack Notification & Emoji Options

SCIM Group Support: Access Control Made Easy at Enterprise Scale

Integrate With External Systems via HTTP Client

Custom Google Doc Permissions

Advanced Slack Customization via Slack Blocks

Notion Projects Integration with Rootly

WhatsApp Integration

Manually Export Action Items to Ticketing Apps (Jira, Zendesk, Linear, and more)

Automated Dashboard Reports

GitHub Secret Scanning Partner

Request for Permission Upgrade

Rootly Joins AWS Marketplace

HashiCorp Vault Integration

Rootly Status Pages V2

Sub-Incidents

Rippling SSO Integration

View Whoโ€™s On-Call