Global vs Custom Settings

Where your Global settings actually are

Globals are not a separate “mystery” page. They are the website-level Settings you already configure when you create the site (and can edit anytime):

1. Open the Cloud Console and select your website.
2. Open Settings (not a single widget).
3. Set the defaults you want everywhere: language, voice, speed / pitch where available, and player-related defaults (controls, panels, animations, and similar options).
4. Save. Those values become Global for every widget that inherits them.

If you want “a clear list of what is Global,” open website Settings — that screen is the list. Widget screens do not re-print the full Global table; they show Use Global when they follow it.

How widgets apply Global vs custom

On almost every widget (Full, Button, Circle, Multi-Page, RHT, Welcome, and custom players) you will see the same pattern:

• Dropdown shows “Use Global” — that field inherits the matching website Setting. Change the Setting once → all Use Global widgets update.
• “Use custom language/voice?” is Disabled — language and voice come from website Settings. Enable it only when this widget needs a different voice or language.
• You pick Enabled / Disabled / a specific option instead of Use Global — that field is now custom for this widget only.

Rule of thumb: leave fields on Use Global unless you have a reason to diverge. Defaults after Cloud activation are built that way on purpose — one brand voice and one player behavior across the site.

1. Open any widget → check a Player or Voice field that shows Use Global.
2. Change the related value in website Settings → Save.
3. Hard-reload a page that uses that widget — the inherited behavior follows the new Global.

When to set custom on one widget

Use a custom override when one player must behave differently from the rest of the site — not when you are still deciding the brand default.

• Different voice for a promo / Welcome line — enable Use custom language/voice? on that widget only. See Change voice & language.
• Different player chrome — switch Speed control, Volume, Text panel, Download, Appear animation, Multiple voices, and similar fields off Use Global and pick Enabled / Disabled / a specific animation for that widget.
• Same everywhere — keep Use Global; edit website Settings instead of copying the same custom value into every widget.

1. Open the widget that must differ.
2. For voice/language: enable Use custom language/voice? and choose language / voice → Save.
3. For player options: change the field from Use Global to the custom value you need → Save.
4. Test that page only — other widgets still on Use Global should keep the website defaults.

“What am I hearing / seeing?” — quick check

1. Website Settings — confirm the Global language, voice, and player defaults you expect.
2. Open the widget on that page — for each important field, is it Use Global or a custom value?
3. Use Global → the live player follows website Settings. Change Settings if the default is wrong.
4. Custom → the live player follows that widget’s override. Change the widget (or switch back to Use Global) if the override is wrong.
5. Hard-reload the live page after Save (browser HTML cache can keep an old view briefly).