> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt
> Use this file to discover all available pages before exploring further.
# Personal Settings
> Set personal contact information, notification preferences, and API keys
## Accessing Personal Center
***
Hover over the user icon in the lower left corner, select **Basic Information** or click **Platform Management**.
## Basic Information
***
| Configuration | Description |
| ---------------------- | ---------------------------------------------- |
| **Account Type** | Primary account or member account |
| **Nickname** | Supports Chinese and English, used for display |
| **Email/Phone Number** | Verification code required when modifying |
For supported phone number regions, refer to [FAQ](/en/on-call/quickstart/faq).
## Notification Preferences
***
Configure different notification methods by alert severity. The system supports setting notification channels separately for **Critical**, **Warning**, and **Info** severity levels.
You can select the following notification channels for each level:
| Channel Type | Description |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Voice** | Notify via phone call |
| **SMS** | Notify via text message |
| **Email** | Send notifications via email |
| **Flashduty APP** | Push notifications through the Flashduty mobile app |
| **IM Apps** | Send notifications through integrated DingTalk, Feishu/Lark, WeCom, **Slack**, or Microsoft Teams apps. For each IM type, you can further pick a **specific integration instance** (for example, if your tenant has multiple Feishu apps, you can choose which one to use) |
In some **private deployment** environments, the operator may have disabled voice, SMS, and APP push notifications (product config `disablePhone`). In that case, only **Email** and **IM Apps** remain in the personal notification channel dropdown — this is expected behavior.
Personal preferences are only used when:
* Incident is directly assigned to an individual, or
* Escalation rule is set to "Direct Message + Follow Personal Preferences"
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.
## APP Key
***
APP Keys are used for API request authentication.
| Limit | Description |
| -------------------- | ------------------------------------------------ |
| **Maximum Count** | Up to 5 per account |
| **Permission Scope** | Has all API operation permissions |
| **Security Note** | Only displayed at creation, please save securely |
* APP Key leakage may cause data security risks, please keep it confidential
* Confirm no business dependencies before deletion; services using that key will fail immediately after deletion
## Flashduty APP
***
### Download the app
| Platform | Download Method |
| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **iOS** | Search "Flashduty" in App Store |
| **Android** | Available on major app stores including Xiaomi, Huawei, Honor, OPPO, and vivo — search "Flashduty" to download (Harmony OS not currently supported) |
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.
Navigate to **Personal Center → Flashduty APP**.
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
The Flashduty APP supports free push notifications for alerts, ensuring critical alerts reach you instantly. You can acknowledge, resolve, and escalate alerts anytime, anywhere 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.
## Related Topics
***
Set notification channel to "Follow Personal Preferences"
Link Feishu/Lark app to receive notifications