> ## Documentation Index > Fetch the complete documentation index at: https://docs.flashduty.com/llms.txt > Use this file to discover all available pages before exploring further. # Flashduty App (Mobile) > Use the Flashduty App and mobile H5 to receive alert notifications and handle incidents anywhere 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](/en/on-call/configuration/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 When visiting the H5 console in a mobile browser, the following sign-in methods are supported: * **Code login**: Receive a verification code via phone or email * **Password login**: Sign in with your account password * **Single sign-on (SSO)**: Enter your enterprise domain or email to locate your organization's authentication method (including LDAP), then complete authentication with your identity provider When you open a Flashduty notification link inside WeCom, Feishu/Lark, or DingTalk, the H5 page signs you in automatically through the platform's authorization mechanism — no need to re-enter account credentials; you land directly on the incident detail. 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: | Filter | Description | | -------------------------------- | --------------------------------------------------------------- | | **Progress** | All / Open / Triggered / Processing / Closed (defaults to Open) | | **Severity** | Critical / Warning / Info, multi-select | | **Incident title / Incident ID** | Fuzzy search by keyword | | **Related to me** | Show only incidents related to you | | **People** | Filter by Creator, Responder, Ack'd by, or Closed by | | **Channel** | Filter by the incident's channel | ### 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: | Action | Description | | ------------------------------- | -------------------------------------------------------------------------------------------- | | **Close** | Close the incident; a closed incident shows **Reopen** instead (a reopen reason is required) | | **Acknowledge / Unacknowledge** | Acknowledge the incident to start working on it; undo if acknowledged by mistake | | **More actions (⋮)** | Expand all supplementary actions, listed below | Available items under **More actions** adapt to the incident's state: | Action | Description | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | **Snooze** | Available for processing incidents; pauses escalation along the escalation rule | | **Escalate** | Available when the incident was assigned via an enabled escalation rule; escalates it to the next level | | **Reassign** | Available for incidents that are not closed; reassigns the incident to another person or schedule | | **Quick silence** | Quickly create a silence rule based on the current incident | | **AI summary** | Generate a summary of the incident handling process (Pro plan) | | **War room** | Create war room, add stakeholders to war room, dissolve war room (Pro plan; requires an IM integration that supports war rooms) | | **Jira and custom actions** | Custom actions such as Jira and ServiceNow configured by admins in integrations | 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**. On Android, notifications are delivered through the Aliyun push channel, with two system notification channels created for incident notifications. Ringtone, vibration, and banner for each channel are managed separately in system notification settings (channel names appear in Chinese): | Notification channel | Description | | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | **故障通知 (Incident notifications)** | The general channel, carrying Warning / Info severity incident notifications | | **紧急通知 (Urgent notifications)** | Only Critical-severity incidents are routed to this channel — visible on the lock screen and able to bypass the system Do Not Disturb mode | Vendor push channels are adapted for Xiaomi and other Chinese manufacturers, so notifications still arrive even when the App is cleared from the background. 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](/en/on-call/configuration/notifications) for details. ## Useful Settings *** Tap the **settings icon** in the upper-right corner of the incident list page to open the settings page: | Setting | Description | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Notifications** | View notification permission status and jump to system notification settings | | **Bypass do not disturb** (iOS) | Jump to system settings to enable Critical Alerts, so Critical incidents are not restricted by Do Not Disturb | | **Sync contacts** | Create a Flashduty contact in your phone's address book and periodically sync voice-notification numbers into it, preventing voice alerts from being misidentified as spam. Only this contact is updated — no other address book information is read or stored | | **Theme** | Follow system / Light / Dark | | **Language** | 中文 / English | | **Check for updates** | Check for a new app-store version; when your version is too old and no longer maintained, an immediate upgrade is required to continue using the App | ## 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. ## Related Reading *** Learn all incident handling methods across console, IM, and voice Configure App push and other notification channels Download the App and manage linked devices