Skip to main content

Accessing personal center

Select your avatar in the lower left corner to open Platform → Personal → Profile. Notification, APP Key, and Flashduty APP are also in the Personal group. For organization settings, go to Platform → Organization → Organization Information.
Personal Center Entry

Personal information

The page shows an account profile card, followed by Display preferences, AI SRE, and Login and security settings.

Account profile card

The card displays the identity of the currently logged-in account:

Display preferences

Time zone controls how times are shown across the console:
  • Member accounts can set their own time zone. Leaving it empty means follow the organization time zone.
  • When the detected browser time zone differs from the effective one, a “Detected you are in zone · Use” hint appears below the selector. Click Use to adopt it; the system never overwrites a time zone you have saved.
  • The subject account has no personal time zone. Its display time zone is the organization time zone, which is changed on the Organization Information page.
The organization time zone is maintained on the Organization Information page by an account with edit permission (the subject account or an Account.Admin; see Permission Design). Changing it affects the time display of every member who follows the organization.

AI SRE

When AI SRE acts as you (for example an automation writes its findings back to an incident, or the agent sends email in your name), the byline is decided here. The two settings cover the incident timeline and email separately: The byline is read once when the action is created and stored with that record, so changing the setting does not rewrite records that already exist. To see the joint byline on the timeline, see Action items and follow-ups.
This group is hidden when only non-On-call modules such as RUM or Status Pages are deployed.

Login & security

Used to log in to this account and to receive alert notifications:
The identity provider maintains the profiles of SSO-synced members, so this page has no edit entries — update profile and role in the identity provider instead.
For supported phone number regions, refer to FAQ.

Notification preferences

The Notification page configures notification channels per notification scene: Incident Dispatch, Collaboration & Follow-up, Schedule Shift, and Internal Status Page. Supported channels per scene: All four scenes support every IM app type (DingTalk, Feishu/Lark, WeCom, Slack, Microsoft Teams). Flashduty APP push and voice are offered only for Incident Dispatch.

Incident dispatch

When an incident is dispatched to you, choose the notification method separately for each severity. The system supports configuring notification channels separately for Critical, Warning, and Info severity levels. You can select the following notification channels for each level:
When an incident is directly assigned to you, Flashduty uses this configuration. For incidents routed by an escalation rule, it applies only when the rule’s direct-message notification is Follow Personal Preferences. See Escalation Rules.
To use DingTalk, WeCom, Feishu/Lark, Slack, or other IM notifications, first complete account linking in the corresponding app. You can select multiple notification channels for each level to ensure important alerts are not missed.

Collaboration & follow-up

How Flashduty notifies you when someone mentions you or assigns you an action item:
  • Collaboration Mention: when others mention you in an incident comment or incident review, Flashduty notifies you through the selected channels. The notification has the comment summary, incident information, and a link to the incident; the same comment never triggers duplicate notifications
  • Work Item Assignment: when someone assigns you an Action or Follow-up, Flashduty notifies you through the selected channels

Schedule shift

When the schedule rotates to you, Flashduty notifies you through the selected channels. SMS, Email, and IM apps are supported.
This configuration applies only when the schedule’s direct-message notification is set to Follow Personal Preferences. See Schedule.

Internal status page

When an internal status page you subscribe to has incident or maintenance updates, Flashduty notifies you through the selected channels. This scene supports IM apps only.
Status-page notifications are pushed only through IM apps; Flashduty sends subscription emails straight to subscribers’ inboxes without reading personal preferences.

APP key

APP Keys authenticate API requests. When creating or editing an APP Key, choose its mode under Permission Scope. To give a script or third-party tool only the access it needs, select Custom permissions and choose its required API scopes. You must select at least one scope before saving. A key’s scope never expands the permissions already granted to your current role.
  • APP Key leakage may cause data security risks, keep it confidential
  • Confirm no business dependencies before deletion; services using that key will fail immediately after deletion

Flashduty APP

Download the app

If your phone brand is not listed above, you can click Download here on the APP management page to get an installation package QR code. Scan it with your phone to download.

Device binding

After installing the app, you need to bind your mobile device to your Flashduty account to receive push notifications.
1

Go to APP management page

Navigate to Personal Center → Flashduty APP.
2

Scan QR code to bind device

The page displays a QR code. Open the Flashduty APP, tap the “Scan to Login” button, and scan the QR code on the page to complete device binding.
Once bound, the page displays a list of linked devices, including device name, OS version, and device identifier. To unbind a device, hover over the device card and click the Unbind button.
  • Binding a device does not automatically enable notifications — the actual notification method depends on your escalation rule settings
  • After unbinding a device, it will no longer receive push notifications
  • The QR code has an expiration time; the page automatically refreshes to generate a new QR code when it expires

Push notifications

You can acknowledge, resolve, and escalate alerts from your mobile device. We recommend enabling system notification permissions and allowing urgent incident notifications in Do Not Disturb mode to avoid missing important alerts.

FAQ

  1. Check if the channel has escalation rules configured. Without escalation rules, incidents won’t trigger notifications
  2. Check the direct message channel settings in escalation rules. Only “Follow Personal Preferences” mode uses your personalized configuration; “Follow Unified Settings” mode ignores personal preferences
Go to Channel Details → Escalation Rules to view current settings.

Escalation Rules

Set notification channel to “Follow Personal Preferences”

Feishu/Lark Integration

Link Feishu/Lark app to receive notifications