> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/kenai-user-guide/setting-up-a-new-environment/the-kenai-connector/configure-config-json.md).

# Configure config.json

The three config.json entries, where each value comes from, and restarting the service.

The configuration file is at:

```
C:\ProgramData\Kenai\Kenai Connector\config.json
```

{% hint style="info" %}
`ProgramData` is a hidden folder. Show hidden items in File Explorer, or paste the path into the address bar.
{% endhint %}

Copy the file before editing. The helper text in the file marks each insertion point.

## The three entries

Replace the placeholder text only.

```json
"ConnectivityApiKey": "Generate on Kenai DASHBOARD",
"ConnectivityEntityHierarchy": "Retrieve from Kenai Dashboard",
"GLGCSAuthHeader": "GGL-API-KEY provisioned-api-key-value",
```

| Entry                         | Replace                         | Source                 | How to get it                                                                                                                                                                                                                                             |
| ----------------------------- | ------------------------------- | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `ConnectivityApiKey`          | `Generate on Kenai DASHBOARD`   | Kenai dashboard        | **Settings → Platform services → API tokens** → create a token. Name it, set scope to Kenai Connector, select the sites.                                                                                                                                  |
| `ConnectivityEntityHierarchy` | `Retrieve from Kenai Dashboard` | Kenai dashboard        | Organisation navigation, top left → right-click the organisation → copy the site value. See below.                                                                                                                                                        |
| `GLGCSAuthHeader`             | `provisioned-api-key-value`     | Gallagher Configurator | The REST API key created in Gallagher for Kenai. Keep `GGL-API-KEY` and the space in front of it. See [Gallagher operator privileges](/knowledge-hub/kenai-user-guide/setting-up-a-new-environment/the-kenai-connector/gallagher-operator-privileges.md). |

{% hint style="warning" %}
The API token is shown once only. Copy it immediately, and delete any scratch copy afterwards.
{% endhint %}

## Reading the entity hierarchy

<figure><img src="https://957655699-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF1z3yfyDYtuAfBcFYrMh%2Fuploads%2FS20NGZ6OM4LoqZEHTEG2%2Fentity-hierarchy.png?alt=media" alt="Entity hierarchy panel showing organisation ID, root, sites and locations"><figcaption><p>Right-click the organisation to open the entity hierarchy</p></figcaption></figure>

| Level           | What it looks like                             | Use it?                     |
| --------------- | ---------------------------------------------- | --------------------------- |
| Organisation ID | The long string at the top                     | No                          |
| Root hierarchy  | Eight characters on their own                  | No                          |
| **Site**        | **Eight characters, a hash, eight characters** | **Yes. Use the copy icon.** |
| Locations       | Everything indented beneath the site           | No                          |

## Save and restart

1. Save the file back as `config.json` and nothing else. A renamed file (for example `config.json.txt`) will not be read.
2. Go back to Windows Services and start the **Kenai Connector** service.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/kenai-user-guide/setting-up-a-new-environment/the-kenai-connector/configure-config-json.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.