> ## Documentation Index
> Fetch the complete documentation index at: https://docs.livingsecurity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations Overview

> Connect workforce and security data sources, learn how their activity supports human risk signals, and review supported delivery options.

Use **Settings → Integrations** to connect systems that provide workforce and security data to Living Security. The in-product Catalog is the authoritative list of providers available to your organization.

## Choose a Task

<CardGroup cols={2}>
  <Card title="Connect a Provider" icon="plug" href="/integrations/managing/setup">
    Prepare credentials, connect a supported provider, and verify its first sync.
  </Card>

  <Card title="Explore Supported Integrations" icon="grid-2" href="https://www.livingsecurity.com/integrations">
    Browse Living Security's integration directory, then use the setup guide for
    provider-specific prerequisites and permissions.
  </Card>

  <Card title="Upload a CSV" icon="file-csv" href="#upload-csv-data">
    Import identity or activity data from a template or existing CSV file.
  </Card>

  <Card title="Configure Communication Channels" icon="comments" href="/features/communications/channels/overview">
    Set up Email, Slack, Microsoft Teams, or Google Chat delivery.
  </Card>

  <Card title="Configure Webhooks" icon="webhook" href="/integrations/outbound/webhooks">
    Send supported event data to customer-owned webhook endpoints.
  </Card>
</CardGroup>

## Find and connect a provider

Use Catalog search and category filters to find a provider. Each result shows whether the integration is already connected and offers **Connect** or **Manage** as appropriate.

<Info>
  Provider availability changes as integrations are added or enabled. Use the
  in-product Catalog—not a copied provider list—as the source of truth for your
  organization.
</Info>

If a provider is not present, use **Request an Integration**. For systems that can send records directly to Living Security, create a **Custom Push Source** and use its API or CSV workflow.

Start onboarding with an identity provider, then add at least one security integration. See [Administrator Onboarding](/getting-started/onboarding) for the required verification tasks.

## Bring data into Living Security

Connected providers supply workforce and security activity through supported
data streams. Living Security normalizes that activity into a common vocabulary
that can support [human risk signals](/signals/data-sources), analysis, and
risk-reduction workflows.

Administrators can review connection and data-stream health after setup. Run
history, tenant-specific errors, lifecycle operations, and advanced diagnostics
remain in the authenticated documentation.

## Upload CSV data

Use **Upload** for one-time identity or activity imports.

<Steps>
  <Step title="Download the matching template">
    Choose the identity or activity template to see the expected columns and example format.
  </Step>

  <Step title="Select a CSV file">
    Drop the file into the upload area or use the file picker. Living Security
    attempts to detect identity or activity data from the headers. If detection is
    inconclusive, select the type manually.
  </Step>

  <Step title="Confirm the data type and upload">
    Review the selected type before starting the upload. Keep identifiers and
    timestamps in the format shown by the template.
  </Step>

  <Step title="Review the result">
    Upload history uses these terminal and in-progress states:

    | Status                    | Meaning                                                          |
    | ------------------------- | ---------------------------------------------------------------- |
    | **Pending**               | Accepted but not yet processing                                  |
    | **Processing**            | Import is running                                                |
    | **Completed**             | All accepted rows completed successfully                         |
    | **Completed with errors** | Some rows failed; download the error file and correct those rows |
    | **Failed**                | The upload could not complete                                    |
  </Step>
</Steps>

Expand **Column Reference** on the Upload page for supported fields and use the downloadable error file instead of resubmitting successful rows blindly.

## Outbound Delivery and Event Egress

Inbound data integrations, people-facing communications, and outbound event webhooks have different configuration areas:

| Need                                                 | Location                                 |
| ---------------------------------------------------- | ---------------------------------------- |
| Connect workforce or security data                   | **Settings → Integrations**              |
| Deliver email, Slack, Teams, or Google Chat messages | **Settings → Communications → Channels** |
| Configure supported event webhooks                   | **Settings → Integrations → Webhooks**   |

Availability can depend on your organization's entitlements and enabled capabilities.

## Related

<CardGroup cols={2}>
  <Card title="Setting Up Integrations" icon="plug" href="/integrations/managing/setup">
    Connect a provider and verify its first data run.
  </Card>

  <Card title="Signal Data Sources" icon="wave-pulse" href="/signals/data-sources">
    Learn how connected systems supply activity for human risk signals.
  </Card>

  <Card title="Communication Channels" icon="comments" href="/features/communications/channels/overview">
    Configure people-facing delivery channels.
  </Card>

  <Card title="Outbound Webhooks" icon="webhook" href="/integrations/outbound/webhooks">
    Configure supported event egress.
  </Card>
</CardGroup>