> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/ide-keys.md).

# IDE Keys

**IDE keys** lists the IDE (developer) keys assigned to your workspace's licence. Each key counts as one licence seat and is linked to one developer, who pastes it into the IZ IDE extension. A key's usage is how many projects that developer can scan from the IDE. Use this tab to assign keys, follow their usage and review the projects scanned with them.

Open it from **Administration** → **Global Settings** → **IDE keys** in the sidebar.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FPrruFvLAm9HJiRLBLllu%2Fv2-gs-ide-keys.png?alt=media&amp;token=f6894522-5fb1-4231-9c4f-2f163ab9744d" alt="IDE keys tab with summary tiles, filters and the key inventory"><figcaption><p>IDE keys</p></figcaption></figure>

{% hint style="warning" %}
You need a role that can view global settings to open this tab, and a role that can invite users to assign keys.
{% endhint %}

## Summary Tiles

Click a tile to filter the inventory.

| Tile           | Shows                         |
| -------------- | ----------------------------- |
| **Total keys** | All keys in your licence.     |
| **Assigned**   | Keys linked to a developer.   |
| **Unassigned** | Keys not linked to anyone.    |
| **Disabled**   | Keys disabled by the licence. |

**Refresh keys** reads the keys from the IZ licence service again. Use it when keys were added to your licence recently.

## Filters

| Filter            | Description                                                                    |
| ----------------- | ------------------------------------------------------------------------------ |
| **STATUS**        | **All**, **Enabled** or **Disabled**.                                          |
| **ASSIGNMENT**    | **Assigned** or **Unassigned**.                                                |
| **ASSIGNED TO**   | One or more people.                                                            |
| **Saved filters** | Pick a saved filter combination, or **Save filters** to store the current one. |

## IDE Key Inventory

Use **Search by key, person or email** to filter the table. The number of keys, **Refresh**, **Columns** (choose the columns to show) and **Export** sit beside it.

| Column          | Description                                                                                                                                                                            |
| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **IDE key**     | The key, masked except for its last characters, and when it was added. Click it to open the key.                                                                                       |
| **Assigned to** | The person's name and email, or **Unassigned**.                                                                                                                                        |
| **Status**      | **Enabled** or **Disabled**.                                                                                                                                                           |
| **Usage**       | Projects scanned with the key out of the number of projects the developer can scan from the IDE, for example `6 / 1,000`, with a progress bar. **No allowance** when the key has none. |
| **Actions**     | **Assign key** or **Reassign key**, and **Scanned projects**, which opens the projects scanned with the key.                                                                           |

The key drawer shows the status, usage, assignee and date added, and the full key under **Key for the IDE extension** with a copy button.

{% hint style="danger" %}
Treat a key like a licence seat: share it only with its assignee.
{% endhint %}

## Assign a Key

1. Click **Assign key** (or **Reassign key**) on the key's row.
2. In **Person**, search for an enabled person by name or email and select them.
3. Click **Assign key**.

The person then finds the key under **My account** → **IDE projects**, pastes it into the IZ IDE extension, and sees the projects it scans in their account.

{% hint style="warning" %}
When you reassign a key, the previous assignee loses access to its project history.
{% endhint %}

## Scanned Projects

**Scanned projects** on a key's row opens **Projects scanned with IDE key** for that key. It lists the projects the developer scanned with the key. Each project is recorded when the IDE extension publishes a scan. Results are the developer's local scan, not a server assessment.

<figure><img src="https://content.gitbook.com/content/9vAxMuDrkUkB4OXlH9CL/blobs/gWnSFLOXIGSjNx3kGgHJ/.gitbook/assets/gs-ide-keys-projects.png" alt="Projects scanned with an IDE key, with project names and paths, last published scan and Results"><figcaption><p>Projects scanned with an IDE key</p></figcaption></figure>

Use **Search by project name or path** to find a project. The number of records and **Refresh** sit beside it.

| Column                  | Description                                                                 |
| ----------------------- | --------------------------------------------------------------------------- |
| **Project**             | The project name and its path on the developer's machine.                   |
| **Last published scan** | When the extension last published a scan of the project, with how long ago. |
| **Results**             | **Review results** opens the project's results.                             |

Click **Back to ide keys** or **IDE key inventory** to return to the key list.

## Review Results

Click **Review results** on a project (or the project name) to open its results in a drawer. The drawer shows:

| Area                                                                  | Description                                                                                                              |
| --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| **Latest published scan**                                             | When the latest scan was published.                                                                                      |
| **Total issues**                                                      | All issues in the latest scan.                                                                                           |
| **Blocker / critical**                                                | Blocker and critical issues.                                                                                             |
| **Major / minor / info**                                              | Major, minor and info issues.                                                                                            |
| **Vulnerabilities**, **Bugs**, **Code smells**, **Security hotspots** | Issues by type.                                                                                                          |
| **Recent scans**                                                      | The 10 most recent published scans, by date: **Scanned**, **Issues**, **Blocker**, **Critical** and **Vulnerabilities**. |
| **Project path**                                                      | Expand it to see the project's full path.                                                                                |

<figure><img src="https://content.gitbook.com/content/9vAxMuDrkUkB4OXlH9CL/blobs/meSLDykIigMkp3Tk76Nh/.gitbook/assets/gs-ide-keys-review.png" alt="Review results drawer with the latest scan&#x27;s counts and the recent scans by date"><figcaption><p>Review results</p></figcaption></figure>

## Next Steps

* [IDE Projects](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/my-account/ide-projects.md): what developers see for their assigned keys.
* [Subscription](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/subscription.md): review the rest of your licence.
* [Global Settings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings.md): the other configuration screens.


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/ide-keys.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.
