> 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/my-account/ide-projects.md).

# IDE Projects

**IDE projects** lists the IDE keys assigned to you. You paste a key into the IZ IDE extension; the projects you scan in your editor then appear here once the extension publishes a scan. A key's usage is how many projects you can scan from the IDE with it.

Open it from **Administration** → **My Account** → **IDE projects** in the sidebar, or from the **IDE projects** tab of My Account.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fl4CfxjrsajF167wdMYDq%2Fv2-account-ide-projects.png?alt=media&amp;token=eced0c96-e8ba-4b8e-9b1e-240e61006b35" alt="Your IDE keys with key counts and the list of keys assigned to you"><figcaption><p>Your IDE keys</p></figcaption></figure>

{% hint style="info" %}
IDE keys come from your organization's licence, and an administrator assigns them to people in [IDE Keys](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/ide-keys.md). If no key is assigned to you, the page says **No IDE keys are assigned to you**; ask an administrator to assign one.
{% endhint %}

## Key Counts

| Tile           | What it shows                   |
| -------------- | ------------------------------- |
| **Total keys** | Keys assigned to your account.  |
| **Assigned**   | Keys linked to a developer.     |
| **Unassigned** | Keys not linked to a developer. |
| **Disabled**   | Keys disabled by the licence.   |

Click a tile to filter the list.

## Your Keys

The **Assigned to you** panel lists your keys.

| Control                              | What it does                          |
| ------------------------------------ | ------------------------------------- |
| **Status**                           | **All**, **Enabled** or **Disabled**. |
| **Saved filters** / **Save filters** | Re-apply or save the current filters. |
| **Search your keys**                 | Finds a key.                          |
| **Refresh**                          | Reloads the list.                     |
| **Columns**                          | Shows or hides columns.               |
| **Export**                           | Downloads the list.                   |

| Column      | Description                                                                                                                                                              |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **IDE key** | The key, masked to its last six characters, and when it was added. Click it to open its details.                                                                         |
| **Status**  | **Enabled** or **Disabled**.                                                                                                                                             |
| **Usage**   | Projects scanned with the key out of the number of projects you can scan from the IDE, for example `1 / 1,000`. The allowance can be **Unlimited**, or **No allowance**. |
| **Actions** | **Scanned projects** opens the projects scanned with this key.                                                                                                           |

## Copy a Key into the IDE Extension

1. Click the masked key.
2. In the key's drawer, check **Status**, **Usage**, **Assigned to** and **Added**.
3. Under **Key for the IDE extension**, click the copy icon.
4. Paste the key into the IZ IDE extension settings.

{% hint style="danger" %}
Treat an IDE key like a licence seat: share it only with the person it is assigned to.
{% endhint %}

## Review Scanned Projects

1. Click **Scanned projects** for a key.
2. The page **Projects scanned with IDE key** lists each project with its **Last published scan**. Use **Search by project name or path** to find one.
3. Click a project, or **Review results**, to open its results.

The project drawer shows the latest published scan (**Total issues**, **Blocker / critical**, **Major / minor / info**, **Vulnerabilities**, **Bugs**, **Code smells** and **Security hotspots**) and **Recent scans**: the 10 most recent published scans by date, with **Issues**, **Blocker**, **Critical** and **Vulnerabilities**. Expand **Project path** for the project's full path.

Results are the developer's local scan in the editor, not a server assessment. Click **Your IDE keys** to return.

## Next Steps

* [Security Credentials](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/my-account/security-credentials.md): tokens for your other integrations.
* [My Activity](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/my-account/my-activity.md): review what your account did.
* [My Account](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/my-account.md): back to the overview.


---

# 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/my-account/ide-projects.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.
