Skip to main content
Flashduty provides mobile capabilities across iOS, Android, and mobile H5. Wherever you are, you can receive incident notifications on your phone and perform all core handling actions — acknowledge, close, escalate, reassign, and more.

​
Download and Install

For download and installation options (App Store, major Android app stores, QR-code package download), see Personal Settings - Flashduty APP. Once installed, your first successful sign-in automatically binds the device to your account, and push notifications start working from then on. You can view and manage linked devices on the console’s Personal Center → Flashduty APP page.

​
Sign-in Methods

The App sign-in page offers two methods:
  • Scan to sign in: Tap Scan to sign in and scan the QR code shown on the console’s Personal Center → Flashduty APP page. Signing in this way also completes device binding. On-premises environments are onboarded the same way — the App reads the service address from the QR code
  • Direct sign in: Tap Direct sign in and complete account verification on the sign-in page opened inside the App. Verification code, password, and single sign-on (SSO) are supported. For on-premises deployments, use Custom sign in domain on the sign-in page to point at your own service address
You can switch between 中文 and English anytime from the upper-right corner of the sign-in page.

​
Incident Handling

​
Incident List and Filters

The App home page is the incident list, split into two tabs: Assigned to me (with an incident-count badge) and All. Swipe left on an incident card to quickly Acknowledge or Close it. Tap the filter icon in the upper-right of the list to combine the following filters. Your filter choices are saved on the device:

​
Incident Detail and Actions

Tap an incident to open its detail page, which has two tabs — Overview (title, severity, description, labels, custom fields, related alerts, war room entry, and more) and Timeline (handling history and comments) — with persistent actions at the bottom: Available items under More actions adapt to the incident’s state:
Consistent with the console: if an admin has configured a custom form for actions such as acknowledge or close, performing these actions in the App requires filling out the form first.

​
Manually Create an Incident

Tap the create button on the incident list page to manually create an incident: fill in the incident title, severity, and description (up to 200 characters), choose a channel and an assignment type (policy assignment or direct assignment to a person). Custom fields such as image upload are supported. Once created, the system immediately dispatches notifications via the selected method.

​
Push Notifications

After you sign in, the current device is bound to your account automatically and starts receiving pushes. Tapping a notification opens the corresponding incident detail page directly.
On iOS, Flashduty uses Apple’s official Critical Alerts capability: notifications for Critical-severity incidents can break through silent and Do Not Disturb modes.Go to Settings → Bypass do not disturb in the App, or enable Critical Alerts in the system Settings → Notifications → Flashduty.
If pushes are not arriving, check in order: whether system notification permission is granted to Flashduty → whether your escalation rule includes the App push channel → (when the rule is set to “Follow Personal Preferences”) whether Flashduty APP is selected in your personal notification preferences. See Notification Channels for details.

​
Useful Settings

Tap the settings icon in the upper-right corner of the incident list page to open the settings page:

​
Mobile H5

m.console.flashcat.cloud is the web build from the same codebase as the App, with identical capabilities:
  • Landing page for notification links: incident-related links in SMS and IM messages (such as comment @mention notifications) open the incident detail page on H5 on mobile devices
  • Embedded in IM: opened inside WeCom, Feishu/Lark, or DingTalk, it signs in automatically so you can handle incidents directly
  • Browser access: visiting it directly in a mobile browser requires signing in first (verification code, password, or SSO)

​
Capability Boundaries

The mobile side focuses on receiving notifications and handling incidents. The following configuration capabilities require the PC console:
  • Schedules, escalation rules, integration setup, and routing rules
  • Notification templates, silence and grouping, and other noise-reduction configuration
  • Personal notification preferences, contact binding, and other account settings
App push is offered only for the incident dispatch scenario. Collaboration notifications such as comment @mentions and work-item assignment do not offer App push — choose SMS, email, or IM under Personal Center → Notification Preferences in the PC console.

Handle and Update Incidents

Learn all incident handling methods across console, IM, and voice

Notification Channels

Configure App push and other notification channels

Personal Settings

Download the App and manage linked devices