> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/plugins/introduction-to-plugins/how-to-add-plugins-to-your-organization.md).

# How to Add Plugins to Your Organization

## Obtaining Your API Key

In order to add plugins to you organization, you will need to have an API key associated with your account.

Follow the steps below to generate your API key:

{% stepper %}
{% step %}

#### Go to API Page

Your Profile → Account → API
{% endstep %}

{% step %}

#### Create API Key

Click 'Create Key' to generate a new API key
{% endstep %}
{% endstepper %}

{% hint style="info" %}
For more details, please refer to [Get Your API Key](/how-to/get-your-api-key.md) page.
{% endhint %}

## Adding Plugins to Your Organization

Ango Hub offers a centralized repository of plugins, known as the Plugin Directory. This is where users can discover, contribute, and share plugins to extend the platform’s functionality.

The Plugin Directory allows you to browse and install custom plugins developed by Ango Hub users, and easily add them to your own organization.

{% hint style="warning" %}
Unless otherwise specified, plugins available in the Plugin Directory are not reviewed or officially maintained by Ango Team. Use plugins from the Plugin Directory at your own risk.
{% endhint %}

#### To access the Plugin Directory:

1. Navigate to Plugins from the top navigation bar.
2. Select Organization Plugins.
3. Click Show Plugin Directory to explore available plugins.

<figure><img src="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2FjLFJf9rXqbsRmTj8DrSw%2Fimage.png?alt=media&amp;token=70ac2266-c29c-4e7d-912a-76a6039ae53b" alt=""><figcaption><p>How to Open Plugin Directory</p></figcaption></figure>

{% hint style="info" %}
The Plugin Directory shows all **Public** plugins and **Listed Private** plugins shared with your organization.
{% endhint %}

Clicking **'Add'** button below a plugin will instantly add it to your organization.

<figure><img src="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2FNoY9uVd3UIIpdztCI4zJ%2FPlugin%20Directory.png?alt=media&amp;token=5a58808d-eba8-4ba1-9c4b-599bef6c09d3" alt=""><figcaption><p>Plugin Directory</p></figcaption></figure>

\
Added plugins will appear in the **Organization Plugins** page:

<figure><img src="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2Fl6FOstly2zPVDTKt0RSB%2Fimage.png?alt=media&amp;token=da12ad6c-18ac-4830-9eb7-26286cdd6ba4" alt=""><figcaption><p>Organization Plugins</p></figcaption></figure>


---

# 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://docs.imerit.net/plugins/introduction-to-plugins/how-to-add-plugins-to-your-organization.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.
