Skip to main content
Whether you are working with demo data or waiting on data integrations, you can configure the platform now. When you are ready, we load your historical data, your users become Learners, and you launch your program.
Time: about an hour, spread across teams · Requires: admin access, plus IT for the allowlisting and sender-domain steps.
Each step below links to the full instructions and ends with the check that tells you it worked. The first two unblock everything that sends email, so do them first.
This page is readable without signing in. The detailed pages it links to are not — sign in to your Living Security account to open them.
1

Brand the platform

Go to Settings → Brand. On the Visual tab, upload your Primary Logo, Dark Mode Logo, and Icon — the Icon is the compact version used for favicons and small displays — then set your primary, secondary, and accent colors. The DNA tab covers Brand DNA.You know it worked when: the Live Preview panel renders your logo and colors on the PDF header and dashboard previews.See Brand Settings. To shape the wording Livvy uses, go to Settings → Livvy → Voice & Tone — see Livvy settings.
2

Send IT the allowlisting details

Do this before launch, not after. Authentication emails carry time-limited login links, so a delayed message can arrive after its link has expired.Give IT the sending address and IP addresses from Authentication Email Delivery, and these domains for content delivery:
You know it worked when: you request a login link for yourself and it arrives while the link is still valid, and platform images and video load without blank frames.
Check the spelling of cdn.contentful.com against whatever list you paste from. A misspelled entry fails silently — the allowlist accepts it, and content simply does not load.
3

Connect your communication channels

Go to Settings → Communications → Channels and connect the paths you want to use: Email, Slack, Microsoft Teams, Google Chat, and In-app notifications inside Engage. Connecting chat channels means nudges reach people where they already work.You know it worked when: every card reads green. Slack, Microsoft Teams, and Google Chat show Connected; In-app shows On; Email shows its sending method — Active · Platform, Active · Your domain, or Active · SMTP. Amber Attention needed on Email means the selected sending method cannot send — either its configuration is incomplete or its credential is failing. Open the card to see which. Send a test from each card that offers one; In-app has no test send, and its panel links to delivery settings instead.See Communication Channels and the Communications Overview.
4

Authenticate your sending domain

Authenticate a domain you control so platform email arrives from you rather than from a vendor. This creates SPF and DKIM DNS records that let recipient mail systems verify we may send on your behalf. You need permission to edit DNS for that domain.You know it worked when: you click Verify on the Sending Domain page, the status updates to verified, and you activate the domain. If you skip this step, tell Learners that notifications come from Living Security at noreply@livingsecurity.ai.See Sending Domain Authentication.
5

Turn on the magic email link for learners

Learners open their training, scorecard, and risk view from a secure, time-limited magic link — no password, no SSO round-trip.Go to Settings → Passwordless Access and turn learner access on. Owners and admins are excluded by default; add your own exclusions for sensitive roles or high-risk cohorts.Once it is on, links replace the sign-in step wherever the platform sends a learner to Engage: training assignment emails, scorecard deliveries, the Engage call-to-action in nudge emails and chat messages, and the continue button on a phishing teachable moment. Links only ever go to a learner’s private destination — their inbox or a one-to-one direct message — never a shared channel.You know it worked when: you click Send me a preview link, choose a channel, and open the link yourself to land straight in the Engage experience a learner sees.
The setting is named Passwordless Access in the product. The magic email link is what it produces.
See Passwordless and External Access.
6

Review and edit the nudge templates

Read the default nudge copy and adjust tone, terminology, and calls to action to match how your organization talks about security. Default copy is a starting point, not a finished voice.You know it worked when: the preview text on each template you edited reads the way your organization speaks.See Nudges.
7

Preview the content, or create your own

Browse the content library to see what your learners will receive. Where the library does not cover something specific to your organization, build custom content.You know it worked when: you can name the modules your first program will assign, and you have flagged any gap the library does not fill.See How to Navigate the Content Studio.

​
If something does not work

  • Login links arrive late or expired — the allowlisting in step 2 is incomplete. Confirm both sending IPs and app@livingsecurity.ai are allowlisted.
  • Images or video do not load — check the content’s own state first. A module’s video area reads Video generation queued, Video is rendering, Video generation failed, or Video ready, and offers Retry video only after a failure — a render in progress has nothing to retry. If the content is ready and still does not appear, a content-delivery domain is missing or misspelled — cdn.contentful.com is the usual culprit.
  • A learner gets a sign-in prompt instead of a magic link — they may be excluded. Owners and admins are excluded by default, and a learner who drifts into an excluded cohort loses links automatically.
  • Email still comes from Living Security — the sending domain is verified but not activated, or step 4 was skipped.

​
What this does not cover

This page is the configuration checklist. Two neighbouring tasks live elsewhere: