> ## 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.

# CultureAI

> Connect CultureAI to the Living Security Platform to import security behavior and reporting data.

export const ConnectInPlatform = ({tile, children}) => <Step title="Enter the credentials in the Living Security Platform">
    <p>
      Completed by whoever holds Living Security access — the program owner, or the system
      admin if they've been invited (delegated setup).
    </p>
    <ol>
      <li>
        Go to <strong>Settings → Integrations → Catalog</strong>, find the{' '}
        <strong>{tile}</strong> tile, click <strong>Connect</strong>.
      </li>
      <li>
        Fill in the fields below, then click <strong>Connect</strong>.
      </li>
    </ol>
    {children}
  </Step>;

export const SystemAdminBanner = ({system, recommendDelegated}) => <Note>
    <p>
      <strong>This guide is for your {system} administrator.</strong> It covers creating API
      credentials inside {system}, which requires admin access to {system} — not to the
      Living Security Platform.
    </p>
    <p>
      If you're the Living Security <strong>program owner</strong> and don't administer {system},
      send this page to whoever does. They complete Part A and hand the credentials back to you
      (or enter them directly if you've invited them into the platform).
      {recommendDelegated && <>
          {' '}Because setup produces sensitive key material, we recommend the{' '}
          <strong>delegated setup</strong> path so the secret is never sent back to you.
        </>}
    </p>
  </Note>;

<SystemAdminBanner system="CultureAI" />

## What Living Security needs

| Credential  | Description                                                                                                                                                                  |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **API key** | A key generated from your CultureAI admin console. Living Security sends this key on every request to authenticate to the CultureAI API. It is the only credential required. |

**Scopes:** CultureAI API keys are not scoped — a valid key grants API access. Living Security only reads reporting data; if your CultureAI console offers scope or permission selection when creating a key, grant read-only reporting access.

**Required role:** **Admin** or **Owner** in CultureAI (to manage API access)

### Prerequisites

* You must be signed in to your CultureAI admin console with a role that can manage API access — typically an **Admin** or **Owner** role. If you do not see an API or developer settings area, contact your CultureAI account representative to have API access enabled for your organization.

***

## Part A — In CultureAI

*Your CultureAI administrator completes these steps.*

<Steps>
  <Step title="Generate an API key">
    1. Sign in to your CultureAI admin console.
    2. Open your organization or account settings and locate the **API** (or **API keys** / **Developer**) area.
    3. Create a new API key and give it a descriptive name (e.g., `Living Security Platform`).

    <Note>
      Living Security uses this key for read-only access to the reporting data it ingests from CultureAI. No write access is required. If CultureAI prompts you to choose scopes or permissions, grant only read access to reporting data.
    </Note>

    <Warning>
      CultureAI may display the API key value **only once** when it is created. Copy it immediately and store it in a secure location (e.g., a password vault or secrets manager). If you navigate away without copying it, you will need to generate a new key.
    </Warning>

    <Note>
      If you cannot find where to create an API key, or you are unsure which permissions to grant, contact your CultureAI account representative. Living Security cannot generate CultureAI credentials on your behalf.
    </Note>
  </Step>
</Steps>

***

## Part B — In the Living Security Platform

*The program owner completes this step, or the system admin if using delegated setup.*

<Steps>
  <ConnectInPlatform tile="CultureAI">
    | Field       | Value                   |
    | ----------- | ----------------------- |
    | **API key** | The API key from Part A |
  </ConnectInPlatform>
</Steps>

You are now connected to CultureAI.

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="401 Unauthorized">
    The API key is invalid or has been revoked. Verify the key is correct and has not been regenerated in CultureAI.
  </Accordion>

  <Accordion title="403 Forbidden">
    The API key lacks read access to reporting data. In CultureAI, verify the key is granted read access, or generate a new key with the correct permissions.
  </Accordion>

  <Accordion title="Empty results (200 OK but no data)">
    The API key may lack access to the reporting data Living Security ingests. Confirm with your CultureAI account representative that the key has read access to reporting data.
  </Accordion>
</AccordionGroup>