Set Up an Integration

This guide covers the common setup path for integrations listed under Settings → Integrations → Catalog. Provider-specific fields, permissions, and authentication steps come from the setup guide linked on that provider’s Catalog card.

​

Prerequisites

These roles may be held by the same person. The person entering credentials in Living Security must have an administrator role that permits integration management; do not invite a source-system administrator into Living Security solely on the assumption that a narrowly scoped setup role exists. Before starting:

• Choose the Living Security organization and environment where the connection belongs.
• Open the provider’s Catalog guide and collect its required scopes, redirect URLs, and allowlist requirements.
• Use your organization’s approved secret-sharing process if different people create and enter credentials.
• Never send passwords, client secrets, private keys, or access-key values through email or a support ticket.

​

1. Prepare Provider Credentials

Open Settings → Integrations → Catalog, find the provider, and read its setup guide before creating credentials. Provider authentication can use OAuth consent, an API token, a client ID and secret, a service account, or another provider-supported method. Create only the credentials and scopes named by that provider’s guide.

​

2. Connect the Provider

If the provider rejects authentication, stop and correct the credential, tenant, region, redirect URL, or source-system permissions before continuing.

​

3. Enable Data Streams

Open the connection under Settings → Integrations → Connected. Living Security discovers the sync templates available for that provider and lists them as streams.

1. Review each stream’s name and purpose.
2. Enable only the streams your program needs.
3. Leave unrelated streams paused.
4. Use Sync Now when available to request the first run.

Not every provider offers the same streams or schedule controls. Follow the controls shown on the connection rather than expecting a universal frequency, scope, field-mapping, draft, or activation wizard.

​

4. Verify the First Run

Connection authentication alone does not prove that data is flowing. For onboarding, the Journey Map’s Verify Identity Data Flowing and Verify Integration Data Flowing tasks complete from ingested data. Do not substitute a saved connection for those verification results.

​

Connection Operations

The connection detail page exposes operations supported by that integration: Removing a connection is not the same as deleting data already ingested from it. Review the provider guide or contact Support if data-retention behavior affects your decision.

​

Custom Push Sources

Use Custom Push Source when a system sends data to Living Security rather than being polled through a Catalog connector.

1. Create the source from the bottom of Catalog.
2. Open its detail page under the custom push area.
3. Select the destination stream.
4. Use Upload CSV for a manual batch or Push via API for an automated sender.
5. Preview the file or payload and review the source’s run history after sending.

The source-detail uploader accepts a source CSV file up to 100 MB. Before uploading, the Dashboard splits it client-side into requests of no more than 10 MB and 10,000 rows each. This source-specific uploader is separate from the general Integrations → Upload page for identity and activity templates.

​

Troubleshooting

When contacting Living Security Support, include the organization, provider, connection name, stream, latest run time, and visible error. Do not include secrets.

​

Related