Flashduty Docs
中文EnglishRoadmapAPI官网控制台
中文EnglishRoadmapAPI官网控制台
  1. Platform
  • Introduction
  • On-call
    • Getting Started
      • Quick start
      • FAQ
      • Product Comparison
    • Incidents
      • What is an Incident
      • View Incidents
      • Handle Incidents
      • Escalations and Assignments
      • Custom Fields
      • Custom Actions
      • Alert Noise Reduction
      • Past Incidents
      • Outlier Incidents
    • Configure On-call
      • Channels
      • Integrate Alerts
      • Alert Noise Reduction
      • Escalation Rules
      • Label Enrichment
      • Schedules
      • Templates
      • Service Calendars
      • Preferences
      • Alert Routing
      • Silence and Inhibition
      • Filters
      • Notification Bots
      • Alert Pipeline
    • Advanced Features
      • Referencing Variables
      • Dynamic Assignment
      • Insights
    • Integrations
      • Alerts integration
        • Standard Alert Integration
        • Email Integration
        • Nightingale/FlashCat Integration
        • Prometheus Integration
        • Grafana Integration
        • Zabbix Integration
        • Uptime Kuma Integration
        • Alibaba Cloud ARMS Integration
        • Alibaba Cloud Monitor CM Event Integration
        • Alibaba Cloud Monitor CM Metrics Integration
        • Alibaba Cloud SLS Integration
        • AWS CloudWatch Integration
        • Azure Monitor Integration
        • Baidu Cloud BCM Integration
        • Huawei Cloud CES Integration
        • Influxdata Integration
        • Open Falcon Integration
        • PagerDuty Integration
        • Tencent BlueKing Integration
        • Tencent Cloud CLS Integration
        • Tencent Cloud Monitor CM Integration
        • Tencent Cloud EventBridge
        • OceanBase Integration
        • Graylog Integration
        • Skywalking Integration
        • Sentry Integration
        • Jiankongbao Integration
        • AWS EventBridge Integration
        • Dynatrace Integration
        • Huawei Cloud LTS Integration
        • GCP Integration
        • Splunk Alert Events Integration
        • AppDynamics Alert Integration
        • SolarWinds Alert Events Integration
        • Volcengine CM Alert Events Integration
        • Volcengine CM Event Center Integration
        • Volcengine TLS Integration
        • OpManager Integration
        • Meraki Integration
        • Keep Integration
        • ElastAlert2 Alert Integration
        • StateCloud Alert Events
        • Guance Alert Events
        • Zilliz Alert Events
        • Huawei Cloud APM Alerts
        • zstack integration
      • Change integration
        • Standard Change Event
        • Jira Issue Events
      • IM integration
        • Feishu (Lark) Integration Guide
        • Dingtalk Integration
        • WeCom Integration
        • Slack Integration
        • Microsoft Teams Integration
      • Single Sign-On
        • Authing Integration
        • Keycloak Guide
        • OpenLDAP Guide
      • Webhooks
        • Alert webhook
        • Incident webhook
        • Costom action
  • RUM
    • Getting Started
      • Introduction
      • Quick start
      • FAQ
    • Applications
      • Applications
      • SDK Integration
      • Advanced Configuration
      • Analysis Dashboard
    • Performance Monitoring
      • Overview
      • Metrics
      • Performance Analysis
      • Performance Optimize
    • Error Tracking
      • Overview
      • Error Reporting
      • Issues
      • Source Mapping
      • Error Grouping
      • Issue States
      • Issue Alerting
    • Others
      • Terminology
      • Data Collection
      • Data Security
  • Platform
    • Teams and Members
    • Permissions
    • Single Sign-On
  • Terms
    • Terms of Service
    • User Agreement/Privary Policy
    • SLA
    • Data Security
  1. Platform

Permissions

Flashduty uses two types of permissions: feature permissions and data permissions, which work together in different scenarios.
📌
You must have both feature permissions and data permissions to operate on certain data objects.

Feature Permissions#

📌
Feature permissions: Also known as operation permissions, these permissions determine which features or operations users can access in the system.
Flashduty controls feature permissions based on roles (RBAC). The system comes with the following preset roles (you can also customize roles):
Account.Admin: Account administrator, has all operation permissions except modifying subject information, can assist subject accounts in managing daily affairs.
Tech.Admin: Technical administrator, has access control, operation audit, and all feature permissions not listed in the table below.
Fin.Admin: Financial administrator, has permissions for billing center orders and all feature permissions not listed in the table below.
The current controllable feature permissions are shown in the following table:
Permission PointAccount.AdminTech.AdminFin.Admin
API Key Management✔️
Operation Audit Reading✔️✔️
Monitoring System Event Management✔️
Custom Field Management✔️✔️
Access Control
- Member Management
- Role Management
- SSO Management
✔️✔️
Plan Management
- Plan Management
- Set Balance Alert
- Change Version Expiration Policy
- Enable Monitoring Management
✔️✔️
All Other Features*✔️✔️✔️
💡
Note that all other features* not listed in the table (such as managing channels) are permissions that all users have by default (even if the user hasn't been assigned a role) and don't need to be controlled.

Data Permissions#

📌
Data permissions: Also known as access permissions, these permissions control the scope of data that users can access or view.
Flashduty controls data permissions based on teams and applies them in the following scenarios:
Team Management: Creators, subject accounts, and team members can modify team information and manage team members.
Channel: Creators, subject accounts, and responsible team members of the channel can modify basic information, reduce noise settings, escalation rules, etc.
Schedule Management: Creators, subject accounts, and responsible team members of the schedule can modify basic information, rotation rules, etc.
Template Management: Creators, subject accounts, and responsible team members of the template can modify basic information, channel template configurations, etc.
Service Calendar: Creators, subject accounts, and responsible team members of the service calendar can modify calendar basic information, holiday settings, etc.
When you don't have data permissions for the corresponding resource, the system will show the following prompt:
drawing

FAQ#

I'm an account administrator, why can't I modify channel settings?
Because channels use data permissions, you must be either the creator, subject account, or a member of the responsible team to modify the corresponding channel information.
If the channel hasn't set a responsible team, you can ask the channel creator or subject to set up a team for the channel and invite you to join, then you'll have management permissions for that channel.
Why can a member without any roles handle incidents?
Because it's common for an incident to require multiple teams working together to resolve it. Therefore, Flashduty doesn't have permission controls for handling alerts. All personnel on the platform can view and handle all alerts under the account.
However, we may implement permission controls for handling incidents in the future.

添加官方技术支持微信

在这里,获得使用上的任何帮助,快速上手FlashDuty

微信扫码交流
上一页
Teams and Members
下一页
Single Sign-On
Built with