Back to Changelog
Back to Changelog

June 15, 2023

Integrations

Custom Google Doc Permissions

Custom Google Doc Permissions

🔐 Custom Google Doc Permissions

We're thrilled to announce our latest feature: the ability to update Google Doc permissions via workflows. This will allow InfoSec teams to streamline user permission management in security incidents.

We understand the importance of efficient collaboration and information security. Now equipped with the ability to update Google Doc permissions using workflows, teams can automatically grant and revoke user access to Google Docs.

Let's take a closer look at the key enhancements in this update:

  • Streamlined Permissions Management: We simplified the process of managing and updating Google Doc permissions. You no longer have to navigate to Google Docs to grant or revoke access for users joining the incident. Access can now all be controlled via Slack or the web UI.
  • Enhanced Security with Real-Time Permission Updates: Security incidents require stricter access control. You don’t want non-participating users to have access to private incident documents. The new feature enables you to automatically revoke access as soon as a user is no longer subscribed to the incident. This prevents unwanted lingering access and helps organizations demonstrate compliance with data protection regulations.
  • Improved Team Efficiency: InfoSec teams face significant time constraints due to the critical nature of their incidents. The ability to automatically provision Google Doc access saves valuable time and effort by eliminating the manual process of managing access rights. This automation allows the response team to focus on more critical tasks like mitigating security threats and implementing improved security measures.

InfoSec teams are responsible for safeguarding sensitive information and ensuring that only authorized individuals have access to critical resources. With this new feature, InfoSec teams can effectively manage access control for confidential incident documents. This reduces the risk of unauthorized access and helps maintain the confidentiality of sensitive information

Here's an instructional video to help you get started on automating Google Doc permissions.


🌝 New & Improved

🆕 Introduced notification emails to alert customers on failed token refreshes
💅 Added text to clearly call out which Service or Schedule is displayed on the on-call schedule dialog in Slack
💅 Updated Loom videos in Rootly Docs
🐛 Fixed inability to display Slack dialog when /incident status command is triggered
🐛 Fixed inability to select a single checkbox in Slack notifications setting
🐛 Fixed action item export issue in to Asana integration

Previous post
Previous post
You are viewing the latest post

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

Fields List View and More UX Improvements for Forms & Form Fields

Bulk Actions for Incidents and Workflows

Share and Set Permissions for Rootly Metrics Dashboards

Bulk Edit Task and Follow-up Action Items

Create Fully Custom Slack Forms Using Our New Form Builder

Specify Public vs Internal Incident Titles on Your Rootly Status Pages

Integrate with Multiple Instances of Jira and Confluence

Auto map any user from PagerDuty and Jira to Rootly incidents with new user lookup