Settings are shared across three screens so that each one holds a single group, and each screen saves on its own. The Settings screen carries a signpost card for anyone looking for something that moved.
The Email screen:
- Email Sending. The send method, the From name, From email and Reply to address, the credentials for the method you chose, and Send a test email. See Choosing How Your Emails Are Sent.
- Connect Your Autoresponder. A card for each connection with an enable checkbox, its required fields, a Get details link, its own Test connection button and the Tag by behaviour option. See Connecting Your Autoresponder.
- Send It Even More Places (WP Sync). The outbound webhook URL that receives all seven webinar events, plus an optional signing secret used to sign each request.
The AI screen:
- Connect Your AI. A card per provider, Google Gemini, Anthropic Claude and OpenAI, with its key, model and Test connection button, plus your primary and backup provider. Optional throughout.
- AI Images. The engine behind the AI image buttons on your slides.
The Settings screen:
- Live Streaming. The default live provider for new webinars, either This site, an embedded external stream or Cloudflare Stream. Choosing Cloudflare reveals the Account ID and API token fields plus a Test connection button.
- License. Your key shown masked, its status, who it is licensed to, when it renews and the sites where it is active, with Refresh License Info, a way to free another site's slot and a Deactivate This Site button.
- Appearance. The colour scheme for these screens. Ten schemes are included: Results Amber, WordPress Native, Clean White, Ivory Cream, Snow Light, Developer Dark, Midnight Blue, Ocean Blue, Sunset Warm and Rose Pink. You can also choose Follow the ResultsAiX Hub to use the scheme set there. It previews as you choose, and Save Appearance keeps it. The Host Chat Console pop out windows use the same scheme.
- Help and your account. Cards for your account portal, support, Diagnostics and the training.
How secrets are handled:
Every API key, token and secret is encrypted in your database rather than stored as plain text, using AES-256-GCM where your server supports it. The fields show a masked value, and leaving a masked field untouched keeps the stored key, so you never retype a key by accident.
One practical tip:
Save the page before using any Test connection button. The tests read what is stored, not what is currently typed on screen.