> For the complete documentation index, see [llms.txt](https://kerno.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kerno.gitbook.io/docs/portal/integrations.md).

# Integrations and API keys

Create an API key for non-interactive sign-in, connect GitHub, and pick up the CI workflow from the portal.

The portal's **Settings** section is where you connect Kerno to the rest of your toolchain.

### API key

**Settings → API Key** issues your personal key for the organization you have selected, so you get one key for each organization you belong to. Choose when it expires as you create it, from one hour to never. The expiry can't be changed later, so delete the key and create a new one to change it. The card tells you when a key has expired or is inactive.

The key exists for signing in where a browser cannot open, such as CI or a remote shell. The card gives you a ready-to-copy `kerno login --api-key` command with your key in it. You can also set the key in the environment, and the CLI authenticates on its own:

```bash
export KERNO_API_KEY=<your key>
export KERNO_ORG_ID=<organization id>   # optional, when you belong to several
kerno init -w /absolute/path/to/your/repo
```

`KERNO_ORG_ID` picks the organization when your key belongs to more than one.

{% hint style="warning" %}
An API key authenticates as you. Keep it in your CI provider's secret store, and delete it from the portal if it leaks.
{% endhint %}

### Integrations

**Settings → Integrations** is where Kerno meets the places your code lives and runs.

**CI setup.** The page carries a ready-made workflow you can copy straight into your repository. It runs your existing Kerno tests on every pull request and needs no account, no API key and no agent. The full walkthrough is in [How to Run your Baseline Tests in CI](/docs/guides/run-tests-in-ci.md).

**GitHub.** Where it is available, connecting the Kerno GitHub App to your GitHub organization lets Kerno see the repositories you choose. Only the organization owner can connect or disconnect it. The card shows the connected account and the repositories Kerno can see. Disconnecting revokes Kerno's access, and deleting a Kerno organization revokes it as well.

### What's next

* [Analytics](/docs/portal/analytics.md) to see how testing is going across your repositories.
* [Organizations and Teams](/docs/portal/organizations-and-teams.md) to manage members and roles.