Skip to main content
Onboarding establishes the identity and security data Living Security needs before you run a human risk program. The in-product Journey Map is the source of truth for your organization’s required, optional, and conditional tasks.

Before You Start

You need:
  • Living Security administrator access
  • An administrator for your identity provider
  • An administrator for at least one supported security system
  • Approved credentials and scopes from each source-system owner
  • Microsoft 365 or Slack administration help if you plan to configure those optional channels
Your Journey Map can differ from the examples below. Migration and security-awareness-training tasks appear only when they apply to your organization.

Understand the Journey Map

The Journey Map organizes setup into three phases: Tasks show whether they are required or optional and whether completion is verified automatically or confirmed manually. Complete prerequisite tasks before expecting dependent tasks to unlock.

1. Complete the Welcome Experience

On first sign-in, Living Security may ask about your environment and program goals so the workspace and onboarding path can be personalized.
  1. Answer the questions with the systems your organization actually uses.
  2. Confirm whether you are migrating an existing Living Security Unify program or configuring security awareness training when those questions appear.
  3. Open the onboarding checklist from Home or open Journey Map.
You should see the Getting Started tasks selected for your organization.

2. Connect Your Identity Provider

Connect Identity Provider is a required administrator task. It establishes the people and identities used throughout Workforce.
  1. Open Connect Identity Provider in the Journey Map.
  2. Choose the supported identity provider or SCIM setup path shown for your organization.
  3. Follow the provider-specific guide and use only the required scopes.
  4. Complete authentication and return to Living Security.
An HR system can provide useful workforce attributes, but it is not a universal substitute for the required identity-provider connection.

Verify identity data

The dependent Verify Identity Data Flowing task is checked automatically.
  • Wait for the connection’s first sync to complete.
  • Open Settings → Integrations → Connected and select the connection.
  • Confirm the connection is healthy and its identity stream has a successful run.
  • Open Workforce → People and confirm expected people appear.
Do not manually mark setup complete if the verification task remains incomplete. Review the connection and sync run first.

3. Connect a Security Integration

Connect First Data Integration is also required. Choose an email-security, endpoint, SIEM, identity-security, or other supported source that contributes useful human-risk signals.
  1. Open the task or go to Settings → Integrations → Catalog.
  2. Select a provider and open its setup guide.
  3. Have the source-system administrator create the required credentials.
  4. Click Connect, enter the credentials, and complete authentication.
  5. Open the new connection and enable the streams required for your program.
See Setting Up Integrations for the complete workflow.

Verify security data

The dependent Verify Integration Data Flowing task is checked automatically after a qualifying source sends data.
  • Confirm at least one enabled stream has a successful run.
  • Review run errors before adding another provider.
  • Check Workforce or Intelligence for the data exposed by that integration.
Data availability depends on the provider and the amount of source data. Use the connection’s actual run status instead of relying on a fixed waiting period.

4. Configure Optional Communication Channels

Slack and Microsoft Teams tasks are optional. Configure the channel your workforce will actually use for supported nudges and notifications. Go to Settings → Communications → Channels, open the channel card, and complete its setup and test-send flow.

Microsoft Teams

Coordinate Living Security and Microsoft 365 administrator setup.

Email Delivery

Choose platform, custom-domain, or customer SMTP delivery.

5. Complete Conditional Tasks

Your Journey Map may include:
  • Migrate Unify Configuration and Migrate Historical Data for an approved Unify migration
  • Configure Security Awareness Training when training is part of your selected program
Follow the tasks in the order shown. Migration tasks are completed by the migration workflow; do not recreate migrated configuration manually while a migration is in progress.

6. Complete the Program Assessment

After required Getting Started tasks are complete, open Program Assessment and complete the maturity assessment. Living Security uses the result to identify potential Level Up work. Level Up recommendations can include additional integrations, a risk-based cohort, a phishing simulation, a risk report, or Livvy knowledge configuration. They are improvement opportunities, not substitutes for the required identity and security-data foundation. These settings are not universal onboarding gates, but they improve the production experience:
  • Settings → Brand — organization name, logo, and supported brand choices
  • Settings → Communications — delivery policies, email delivery, and communication history
  • Settings → User Management — platform access for additional administrators
  • Settings → Knowledge — approved organizational context available to supported Livvy experiences

Completion Checklist

  • The Journey Map shows all required Getting Started tasks complete.
  • Identity-provider connection and identity stream are healthy.
  • Expected people appear in Workforce.
  • At least one security integration has a successful data run.
  • Required communication channel test sends succeed, if channels are in scope.
  • Conditional migration or training tasks are complete, if shown.
  • The Program Assessment is available or complete.

Troubleshooting

Open the related connection under Settings → Integrations → Connected. Confirm authentication is healthy, the required stream is enabled, and its latest run succeeded. Automatic verification depends on ingested data, not only on saving credentials.
Ask the source-system administrator to confirm that credentials are current and include every scope named in the provider guide. Reauthorize the connection after changing source-system permissions.
Confirm that the identity stream includes the expected population and inspect any group or source filters. Then check whether the person appears under a different identity before creating duplicates.
Return to Getting Started and complete every required task and its dependent verification task. Optional Slack and Teams tasks do not block the next phase.

Get Help

Contact Living Security Support with your organization, provider, connection name, latest run time, and visible error. Never send access-key secrets, passwords, or private keys in a support request.