Help Center
Advanced Settings
Custom SMTP with inline HTML invitations, tenant runtime branding extraction, selectable theme presets, optional removal of platform branding from respondent-facing surfaces.
What this guide helps you do
Configure workspace-level email, templates, AI behavior, branding, and privacy defaults without surprising live surveys.
Before you start
- Confirm you have admin permission.
- Prepare approved sender, brand, and template copy.
- Know which surveys could be affected by changing defaults.
What you will do
- Align tenant identity
- Operationalize SMTP and templates
- Tune AI connectors
- Validate privacy defaults
- Document changes
You are done when
- Email and template tests pass.
- AI settings match policy and tone.
- Defaults are documented for future admins.
Overview
Granular controls keep long programs consistent: branded respondent surfaces including optional removal of platform marks, selectable theme presets, brand color lifts from uploaded creative, hardened SMTP relays, editable inline HTML invitations, AI-provider governance wired into generation and summaries, multilingual defaults coordinated with Localization, privacy or consent inheritance for every survey, and telemetry hooks that pair with integration monitoring when you run a dedicated instance.
When to use this feature
Step-by-step guide
Align tenant identity
Update logo, palettes, domains, and theme presets, then preview the respondent shell on desktop and mobile across every rolled-out locale.
Operationalize SMTP and templates
Connect approved relays and craft inline HTML for invitations plus reminders with personalization tokens that localization reviewers approve.
Tune AI connectors
Set default models, escalation paths, and custom enterprise endpoints consistent with AI policy.
Validate privacy defaults
Propagate consent language, cookie banners, or retention prompts that match InfoSec guidance before exposing live respondents.
Document changes
Snapshot settings for auditors when dedicated instances host multiple workspaces or overlapping programs.
Admin blast radius
SMTP AI branding tweaks ripple across invitations analytics exports simultaneously.
Screens / UI explanation
Branding removal options only affect respondent surfaces never internal admin diagnostics.
Inline HTML editors require desktop validation plus mobile screenshot sign-off.
Best practices
Stage changes in pilot workspaces before enterprise-wide toggles.
Pair palette extractions with contrast accessibility testing.
Restrict AI credential edits to security-cleared admins.
Tips
Export settings reference sheets after each quarter for auditors.
Mirror SMTP DKIM keys into InfoSec ticket systems when rotating.
Common issues
Branding mismatch after CDN cache.
Hard refresh bust caches confirm DNS targets per region.
SMTP throttling spikes.
Spread mail batches coordinate with quotas distribution pacing.
FAQ
Can each workspace inherit different AI hosts?
Yes subject to billing entitlements segregate credential vaults accordingly.