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
Join Restrictions	Email-domain allowlist controlling who can join the organization through an invitation
Notification Settings	Content and language of system notifications within the organization, applied to all members
Free Notification Quota Reminders	Switches that email the organization’s administrators before the free notification quota runs out or when it does
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
Time Zone	The organization time zone. Members without their own personal time zone see all times in it. Only the subject account or an Account.Admin can change it

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 and do not shift when the organization time zone changes — a rotation written as “09:00 every day” in the schedule’s own time zone stays 09:00 there.
Members can override the display zone for themselves via 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 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 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. Only the subject account or an Account.Admin can edit it; other members see the current configuration as read-only text.

Item	Description
Email domain allowlist	Email domains allowed to join the organization. Type a domain and press Enter to add it; you can add several. Leave it empty for no restriction
Allow subdomains	Appears only when the allowlist contains at least one valid domain; off by default. When enabled, an allowlisted `corp.com` also covers subdomain addresses such as `mail.corp.com`

Matching is case-insensitive: Corp.com and corp.com are the same domain
Each entry must be a full domain (at least one dot, e.g. corp.com): it cannot start or end with a dot or a hyphen, and it cannot contain consecutive dots or a hyphen next to a dot
Saving also checks that your own email domain is on the list; a list that leaves it out is rejected with a prompt to add it

Where It Applies

The email-domain allowlist is checked only on the invite-join path (one-by-one invitations and joins through an invite link / QR code, including the invite-scoped sign-in). It plays no part in regular sign-in or authorization:

Scenario	Allowlist checked?
One-by-one invitation (with an email address)	Yes. An address outside the allowlist is rejected inline in the invite dialog, and the backend rejects it as well
Joining through an invite link / QR code	Yes, against the email domain the invitee signs in with
One-by-one invitation with a phone number only	No. Phone invitations are vouched for by the administrator, so those members can join as usual
Regular sign-in and authorization	No. The allowlist is not part of sign-in or authorization
Members who already joined, and the owner account	Unaffected. They keep signing in and working even if their domain is not on the list, and opening an invite link again lets them straight in

With an allowlist in place, anyone joining through an invite link / QR code must present a verified email address: a phone-only contact with no verified email is rejected with a prompt to verify the address first. In that case the invite sign-in page offers email sign-in only, with the hint “This organization only allows email addresses on its allowlist. Please sign in with your email.”
Organizations that enable SSO-only login cannot be joined through an invite link / QR code: membership is managed by the identity provider, so the join is rejected with a prompt asking the administrator to grant access through SSO.

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.

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; only the subject account or an Account.Admin can change them, and other members see the current values as read-only text.

Switch	Field	Trigger
Remind at 20% remaining	`free_quota_20_reminder_enabled`	Free quota drops to 20% or below while still above 0
Remind when exhausted	`free_quota_exhausted_reminder_enabled`	Free quota reaches 0 for the first time

Both switches are on by default; turning one back on does not backfill — a threshold already crossed while it was off is not reminded again
Only paid accounts (Standard / Pro, not a trial, not expired) are counted, and only notifications actually sent successfully and counted toward the quota — free accounts do not receive this kind of reminder
SMS, voice calls, and emails are counted and reminded separately: at most one reminder per quota period per channel
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)

Quota amounts, overage billing, and what happens when a free quota runs out are covered in Plans and Billing.

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 for more snooze operations.

Quick-silence label exclusion rules

When you create a 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

SSO Configuration

Personal Settings

Set personal notification preferences

Home

Products

Platform

Developer

Compliance

Changelog

Organization Information