website logo
⌘K
Help and Documentation
Introduction to Rootly
Quick Start Guide
Managing Incidents
Manage Action Items
Managing Users
Managing Teams
Status Pages
Timeline
Postmortems
Playbooks
Workflows
Alerts
Pulses
Metrics
API Reference
Webhooks
Liquid
Contacting Support
Integrations
Overview
Slack
Mattermost
PagerDuty
Opsgenie
VictorOps (Splunk On-Call)
Service Now
Nobl9
Jira
Jira ( On premise )
Confluence
Confluence ( On premise )
Google Docs
Notion
Quip
Dropbox Paper
Asana
Linear
Freshservice
Trello
Shortcut ( formerly Clubhouse )
Statuspage.io
Airtable
Zendesk
Zoom
Webex
Microsoft Teams
GoToMeeting
Google Meet
Twitter
GitHub
Gitlab
AWS Elastic Beanstalk
Heroku
Kubernetes
Datadog
Honeycomb
Backstage
New Relic
Looker
Grafana
Email
SMTP
SendGrid
Sentry
Rollbar
Zapier
API
Terraform
Pulumi
HashiCorp Vault
SSO (Okta, Azure, Auth0, etc.)
SCIM
Docs powered by archbee 
3min

Manage Via Slack

Restrictions

  • This option is only available for private incidents
  • This option is only available in an incident channel

How To

You can surface the dialog via the slash command /rootly manage or through the initial blocks button (screenshot below)

Document image


When the dialog is surfaced you have an optional option to remove all users that don't have private incident read access through RBAC. This feature is useful for bulk removing users when trying to descope access for an incident that might have started out public



Document image






Updated 16 Mar 2023
Did this page help you?
Yes
No
UP NEXT
Managing Incident Roles
Docs powered by archbee 
TABLE OF CONTENTS
Restrictions
How To