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

# Linx Security

> Connect Linx Security, an identity governance (IGA) platform, so workflows can read identities, accounts, and applications, and create access requests, through the Linx API - authenticated with OAuth client credentials.

<Note>
  The Linx Security integration is in beta.
</Note>

## About Linx Security

Linx Security is an identity governance and administration (IGA) platform. Serval connects to your Linx tenant with an API client so workflows can read human and non-human identities, accounts, applications, groups, roles, and workflows, create access requests, and reach the rest of the Linx API on demand.

**Authentication:**
OAuth 2.0 client credentials (a Client ID and Client Secret). Serval exchanges them for a short-lived access token at `https://connect.linxsecurity.io/api/authorize` and refreshes it automatically before it expires, so there is no browser redirect and no per-user sign-in.

**Data sync:**
On demand only. There is no background sync and no entity ingestion. Workflows call the Linx API live at `connect.linxsecurity.io` when they run.

## Get your credentials

Contact **Linx Support** to obtain an API Client ID and Client Secret for your tenant. There is no self-serve credential page.

## Connect in Serval

<Steps>
  <Step title="Open the Linx Security connect form">
    In Serval, open the Linx Security integration and start a new connection.
  </Step>

  <Step title="Enter your Client ID (required)">
    Paste the Client ID provided by Linx Support.
  </Step>

  <Step title="Enter your Client Secret (required)">
    Paste the matching Client Secret (a password field).
  </Step>

  <Step title="Save the connection">
    Submit the form. Serval runs the health checks below to confirm the credentials work.
  </Step>
</Steps>

## Verifying the connection

The Linx Security integration ships three health checks, each a lightweight read of a single record:

* **List workflows**, confirming access to the Administrative API.
* **List humans**, confirming access to identity data.
* **List applications**, confirming access to application data.

A passing set confirms Serval can mint a token and read from your Linx tenant.

***

Need help? Contact **[support@serval.com](mailto:support@serval.com)** for assistance with your Linx Security integration.