Skip to main content

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:
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 Admin role can modify settings.

Organization profile

Organization time zone

The organization time zone determines what “organization-following” members see across the console. Changing it requires confirming the blast radius:
  • Every member without a personal time zone switches to the new zone immediately.
  • Organization-level on-call schedules keep their original wall-clock time when the organization time zone changes. A rotation set to “09:00 every day” in the schedule’s time zone stays at 09:00 there.
  • Members can override the display zone for themselves through the Display Preferences section of Personal Settings.

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 through {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 for more information.

Join restrictions

The Join Restrictions section controls who can join the organization through an invitation. It currently offers an email-domain allowlist: only people whose email domain is on the list can join.
  • Enter full domains (for example, corp.com); matching is case-insensitive
  • The list must include your own email domain, or you can’t save it

Where it applies

The allowlist only applies when someone joins the organization; it does not affect regular sign-in:
Organizations that enable SSO-only login cannot be joined through an invite link / QR code; an administrator grants access through SSO instead.

Notification settings

The Notification Settings section maintains the content and language of system notifications within the organization, applied to all members.

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

Send full incident alert SMS

An org-level toggle that controls whether incident alert SMS messages are truncated:
Verification, invitation, and on-call SMS messages are unaffected by this toggle and always follow their original behavior.

Free notification quota reminders

When your free notification quota (SMS / voice call / email) runs low, Flashduty emails the organization’s administrators so notifications do not stop once the quota is used up. This block is available on SaaS only and is not shown on private deployments. Both switches are on by default and can be turned off independently.
  • Turning a switch back on does not backfill thresholds crossed while it was off
  • Flashduty counts only paid accounts (Standard / Pro, not in trial, not expired), and only notifications sent successfully and counted toward the quota. Free accounts don’t get this reminder
  • SMS, voice calls, and emails are counted and reminded separately: at most one reminder per quota period per channel
  • Reminder emails don’t count toward the notification quota
  • Reminders are email-only — no SMS or phone call. They go to the account’s own email address plus the verified email addresses of currently enabled Admin members (up to 20)
For quota amounts, overage billing, and what happens when a free quota runs out, see Plans and Billing.

Readiness requirement

Readiness requirement sets how many high-urgency notification methods every on-call member must have. A member who falls short sees which method is missing in the to-dos on the My On-call panel. Each on-call member’s phone and app status is in the legend on the schedule detail page. How each method is judged:
  • Phone: having a phone number in the member’s profile counts.
  • IM: having any one IM app bound counts.
  • Installing the app alone does not count, because app push is not a high-urgency method.
  • On a self-hosted deployment with the phone turned off, only No extra requirement and Connect IM are available.
Once the bar is set, a member who falls short gets a reminder naming the missing method when they open the My On-call panel, at most once every 24 hours. The reminder goes to the member’s IM when one is bound, otherwise to app push, otherwise to email; a member reachable on none of them gets no reminder. A change applies to every member; regular members can only see the current bar.

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
Saved changes take effect immediately in the console and IM cards. See Snooze for more snooze operations.

Quick-silence label exclusion rules

When you create a quick silence, Flashduty builds the matching conditions from the incident’s severity and labels. It leaves out labels that hit an exclusion rule. Labels whose values change every time (trigger value, current value, links, and so on) would otherwise let similar alerts escape silencing. Where to configure: Organization Information → Incident Handling → Quick-silence excluded labels. Changes apply only to 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 on by default. Flashduty also always excludes label values longer than 235 characters
  • Global blacklist: a built-in set of labels whose values change often (such as trigger_value, current_value, detail_url, query) is always excluded and cannot be configured

SSO Configuration

Login domain and SSO single sign-on

Personal Settings

Set personal notification preferences