> ## 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.
# Organization Information
> View and manage organization profile, notification settings, and incident-handling defaults
## Organization Information
***
The **Organization Information** page centralizes your organization's identity and org-level default settings, and is accessible to all members. Entry: **Platform Management → Organization → Organization Information**, or click the **Organization Information** button on your profile card in Personal Center.
The page contains the following sections:
| Section | Description |
| ------------------------- | ---------------------------------------------------------------------------------------------- |
| **Organization Profile** | Organization logo, name, ID, and domain |
| **Notification Settings** | Content and language of system notifications within the organization, applied to all members |
| **Incident Handling** | Org-level defaults for incident-handling operations, applied to the console and IM alert cards |
This page is **open to all members**: regular members can view every configuration item in read-only mode; only the **subject account** or accounts with the **Account.Admin** role can modify settings.
## Organization Profile
***
The Organization Profile section maintains the organization's identity. Only the subject account or Account.Admin can edit; other members are read-only.
| Item | Description |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Logo** | Organization logo image, set via a **Logo URL** that must be a reachable http/https address; click **Reset to Default Logo** to clear the custom logo and restore the default |
| **Name** | Organization name, displayed in invitation emails and SMS messages |
| **ID** | Unique identifier of the organization; provide it when integrating APIs or contacting support |
| **Domain** | Dedicated subdomain for login and email integration push |
### Domain
The domain is an important identifier for the subject account, used to locate the correct SSO configuration during single sign-on. Each organization's login domain is globally unique. After configuration, members can initiate single sign-on directly via `{domain}.sso.flashcat.cloud`.
Note the following rules when changing the domain:
* The domain must be **5–40 characters** and can only contain letters, numbers, or `-`, and cannot start or end with `-`
* The new domain cannot be the same as the current one
* The change requires confirming the impact scope and may require multi-factor authentication (MFA)
After changing the domain, it applies to the following scenarios:
* **SSO single sign-on configuration**: All configured SSO login domains change accordingly; members must use the new domain to initiate single sign-on
* **Email integration push addresses**: The email integration receiving address format is `prefix@{domain}.{email-suffix}`; the address changes when the domain changes, so update related configurations promptly
See [SSO Configuration](/en/platform/configure-sso) for more information.
## Notification Settings
***
The Notification Settings section maintains the content and language of system notifications within the organization, applied to all members. Only the subject account or Account.Admin can modify; other members see the current values as read-only text.
### Default Notification Language
The org-level default language for system notification copy — **Chinese** or **English** — applied to incident dispatch, schedule shift, subscription expiration reminders, and other system notifications.
* This setting does **not** affect the console UI language
* Verification and invitation emails follow the recipient's browser language and are unaffected by this setting
* This setting previously lived on the personal **Notification Preferences** page; it is now an org-level configuration
### Send Full Incident Alert SMS
An org-level toggle that controls whether incident alert SMS messages are truncated:
| State | Behavior |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
| **Enabled** | Incident alert SMS messages are no longer truncated; long content may be split by carriers into multiple messages, billed per message |
| **Disabled** | Incident alert SMS messages are truncated to a single message length |
Enabling requires confirmation: domestic and international incident alert SMS messages will no longer be truncated, and long content may be split into multiple messages billed separately.
Verification, invitation, and on-call SMS messages are **unaffected** by this toggle and always follow their original behavior.
## Incident Handling
***
The Incident Handling section maintains org-level defaults for incident-handling operations, applied to **the console and IM alert cards**.
### Snooze Time Presets
When snoozing incidents in the console or IM cards (Feishu/Lark, DingTalk, WeCom, Slack, Teams), the system offers 3 preset durations:
* Exactly **3 fixed slots**; each slot uses **hours** or **minutes** as its unit
* Each value must be greater than 0, and at most **24 hours** (max 24 in hours, max 1440 in minutes)
* Presets **cannot be duplicated**
* Defaults are **2 hours / 4 hours / 12 hours**; click **Restore Defaults** to reset quickly
Click **Save** to apply changes, which take effect immediately in the console and IM cards. Only the subject account or Account.Admin can edit; other members see the current presets as read-only text. See [Snooze](/en/on-call/incident/handle-update-incident) for more snooze operations.
### Quick-silence label exclusion rules
When you create a [quick silence](/en/on-call/channel/noise-reduction#quick-silence), the matching conditions are generated automatically from the incident's severity and labels. Labels that hit an exclusion rule do not participate in the matching conditions, so labels whose values change on every occurrence (trigger value, current value, links, etc.) don't end up in the conditions and cause similar alerts to escape silencing.
**Where to configure**: Organization Profile → Fault Handling → **Quick-silence excluded labels** (the configuration dialog is titled "Quick-silence label exclusion rules"). Only the subject account or Account.Admin can modify the rules; other members can open and view the current rules (exclusion rules affect the silences they create, so they need visibility). Changes take effect only for quick silences created afterwards.
Configuration contents:
* **Per-integration exclusion lists**: maintain an excluded label list for each integration separately. When creating a quick silence, a label hitting any exclusion list is excluded
* **System format rule toggles**: `json` (JSON values), `datetime` (datetime format), and `numeric` (numeric values), all enabled by default; label values longer than 235 characters are also excluded automatically (cannot be disabled)
* **Global blacklist**: about 95 system-curated labels (such as `trigger_value`, `current_value`, `detail_url`, `query`) are always excluded; they are maintained as a frontend constant and cannot be configured
## Related Topics
***
Login domain and SSO single sign-on
Set personal notification preferences