Advanced Settings
⏱ ~4 min read · reference — what each setting category does, where changes apply, and how per-site overrides interact with account defaults.
In short. Advanced Settings in SG-Dashboard is the account-tier configuration surface for toggles and preferences that don't belong in Billing, Site Manager, or any other named sub-page. Changes here apply across every site in your account — notification routing, integration defaults, time zone, and operational toggles. Per-site overrides are available where the platform supports them, and an override never erases the account default — it just deviates from it for that one site.
On this page: Where it fits · Setting categories · Scope of changes · Worked examples · FAQ · Related settings
Where it fits
SG-Dashboard is your account-tier control center — the place above any single site. Most of its sub-pages have a clear job: Billing handles your subscription and payment, Site Manager lists and opens your sites, Client Manager routes work across clients. Advanced Settings is where the remaining account-wide preferences live — the toggles and defaults that apply to your whole account rather than to one site. If a setting controls how your account behaves everywhere and doesn't belong on a named page, this is where you'll find it.
Because these settings sit at the account tier, a change here is broad by default. That's the point: set a preference once and have it carry across every site, instead of repeating yourself on each one.
Setting categories
Advanced Settings groups account-tier configuration into four categories. The table below is the quick map; each section under it explains what the category controls and where the change lands.
| Category | What it controls | Where the change applies |
|---|---|---|
| Notification preferences | Which channels deliver which account-wide alerts, suppression rules, and recipient defaults | Account-wide |
| Integration defaults | Default behavior for connected integrations on newly provisioned sites | New sites inherit; existing sites keep their own config |
| Account preferences | Time zone, locale, and the default role for new team invitations | Account-wide; flows into report timestamps and schedules |
| Operational toggles | Account-wide behavior switches such as debug logging and audit retention | Account-wide, where your plan supports them |
Notification preferences
Account-tier notification routing — which channels deliver which event categories, suppression rules, and recipient defaults. Control whether account-wide alerts arrive by email, in-app, or as a daily digest rollup.
Integration defaults
Account-tier defaults for connected integrations — default property pairing for new sites, sync cadence, and healthy-connection thresholds. New sites provisioned after a change here inherit the updated default; existing sites keep their per-site configuration unless you update them.
Account preferences
Time zone, locale, and the default operator role assigned when you invite a new team member. Changes here flow through to report timestamps and scheduled-process boundaries account-wide.
Operational toggles
Account-wide behavior toggles — debug logging and audit retention overrides where your plan supports them. Because these affect how your account records and retains operational data, they're the category to reach for least often; change them deliberately, not casually.
Account · Advanced settings
Account-tier preferences
Notification preferences
Email account-wide alerts●
In-app account-wide alerts●
Daily digest rollup○
Account preferences
Time zoneUTC+08 Manila
Localeen-US
Default operator role for new invitationsEditor
Scope of changes
The single most useful thing to understand about Advanced Settings is how far a change reaches. There are two patterns, and knowing which applies saves a lot of second-guessing.
Most changes apply account-wide. Notification routing, integration defaults, and account preferences propagate across every site under the account. Set the time zone once and it applies everywhere; toggle a notification rule and it governs alerts for the whole account. This is the default behavior and why these settings live at the account tier rather than on a single site.
Per-site overrides are supported where the platform allows it. Some settings can be overridden inside a particular site's Configuration. The value you set in Advanced Settings is the account-tier default; a site admin can deviate from it for that one site. The important detail: an override does not overwrite the account setting. The account default stays in place and continues to apply to every site that hasn't set its own override. So you can have one account-wide default and a small number of sites that intentionally differ, without the two fighting each other.
There's also a timing nuance for integration defaults. A change to an integration default affects new sites provisioned after the change — those sites inherit the updated default. Sites that already exist keep their current per-site configuration unless you update each one. If you want a new default to take hold everywhere, plan to revisit existing sites, or set the default before you provision the sites that should inherit it.
Examples
Changing the account time zone. Open Advanced Settings → Account preferences, update the time zone to UTC+08 Manila. Report timestamps and scheduled-process boundaries update account-wide immediately.
Suppressing the email digest. Open Advanced Settings → Notification preferences, toggle off Daily digest rollup. In-app alerts continue; the digest email stops.
Setting an integration default before provisioning new sites. Set the default GA4 property pairing convention before you provision new sites. Those sites inherit the default automatically; existing sites are unaffected unless updated.
Letting one site differ from the account default. Set the account-wide default — say, a default operator role of Editor — then have a site admin set a different role inside that site's Configuration. The account default stays Editor for every other site; only the one site deviates.
FAQ
If I change a setting here, does it touch sites that already exist?
It depends on the category. Notification routing and account preferences apply account-wide right away. Integration defaults apply to sites provisioned after the change — existing sites keep their own configuration until you update them.
Will an override on one site change my account default?
No. An override only changes that one site. The account-tier value remains the default for every site that hasn't set its own override.
Why isn't a billing or site-specific setting here?
Advanced Settings is for account-wide preferences that don't belong on a named page. Subscription and payment settings live in Billing; anything specific to a single site lives in that site's Configuration. See the related surfaces below.
Related settings
- SG-Dashboard Overview — parent surface.
- Billing Overview — billing-related configuration (separate surface).
- Client Manager — multi-client routing (separate surface).