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

# 1Password integration setup

> Connect the 1Password Events API to Living Security for account, authentication, administrative, and credential-vault activity.

export const PublicIntegrationNextSteps = () => <>
    <hr />
    <h2>Related resources</h2>
    <ul>
      <li>
        <a href="/signals/data-sources">Learn how integration data becomes Human Risk Management signals</a>
      </li>
      <li>
        <a href="https://www.livingsecurity.com/integrations">Explore Living Security integrations</a>
      </li>
      <li>
        <a href="https://app.livingsecurity.ai/">Open the Living Security Platform</a>
      </li>
      <li>
        <a href="https://www.livingsecurity.com/request-demo/">Request a Living Security demo</a>
      </li>
    </ul>
  </>;

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="1Password" recommendDelegated={true} />

## What this integration contributes

1Password can contribute normalized account, authentication, administrative, and credential-vault activity. Reviewed examples include:

* `mfa.factor.activated` — activates additional MFA factors
* `credential.vault.created` — adds entries to the credential vault
* `credential.downloaded` — credential exported

See [how integration data becomes signals](/signals/data-sources).

## What Living Security needs

| Credential                  | Description                                                                               |
| --------------------------- | ----------------------------------------------------------------------------------------- |
| **Events API bearer token** | A token issued for an Events Reporting integration.                                       |
| **Events API host**         | The host for your 1Password account, such as `events.1password.com`. Enter the host only. |

Select access to **sign-in attempts**, **item usages**, and **audit events** when issuing the token. A 1Password Business owner or administrator must create the integration.

## Setup

<Steps>
  <Step title="Create an Events Reporting integration in 1Password">
    In the 1Password web app, open **Integrations**, choose **Events Reporting**, and add an integration for **Other**. Give it a recognizable name such as **Living Security**.
  </Step>

  <Step title="Issue a bearer token">
    Select sign-in attempts, item usages, and audit events. Set an expiration that matches your credential-rotation policy, issue the token, and save it securely. 1Password displays the token once.
  </Step>

  <ConnectInPlatform tile="1Password Events API">
    Enter the Events API host and bearer token. Do not include `https://` or a trailing slash in the host.
  </ConnectInPlatform>
</Steps>

## Verify and troubleshoot

After connecting, verify that the connection test succeeds and that the first synchronization begins. A successful connection can initially report zero records when the selected event types have no recent activity.

<AccordionGroup>
  <Accordion title="401 Unauthorized">
    The token is invalid, expired, or revoked. Issue a new token from the Events Reporting integration and reconnect.
  </Accordion>

  <Accordion title="Events are missing">
    Edit or replace the token and confirm that sign-in attempts, item usages, and audit events are selected.
  </Accordion>

  <Accordion title="The host is rejected">
    Use the Events API host for your account without `https://` or a trailing slash. The host can differ for regional or enterprise environments.
  </Accordion>
</AccordionGroup>

For vendor-side details, see [1Password's Events API setup guide](https://www.1password.dev/events-api/get-started).

<PublicIntegrationNextSteps />