> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infinity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infinity/user-guide/marketplace.md).

# Marketplace

The Marketplace module allows users to integrate **third-party applications** and platform extensions with Infraon products. It provides centralized access to supported integrations, AI-powered applications, communication platforms, directory services, automation tools, and asset management integrations.

Marketplace applications are available based on the subscribed product plan and license entitlement. Depending on the selected plan, users can access, configure, and manage supported integrations directly from the Marketplace page.

## **License Management**

Marketplace integrations are controlled through **product-based licensing plans**. Application availability depends on the subscribed edition and determines whether an integration can be accessed, configured, or upgraded.

Users without the required license will see an Upgrade badge on the application card, and the integration will remain inaccessible until the appropriate plan is enabled.

The following plans are supported:

| Integration              | ITSM | Assets | UNMS | Helpdesk | NMS |
| ------------------------ | ---- | ------ | ---- | -------- | --- |
| Std                      | Pro  | Ent    | Pro  | Ent      | Pro |
| **AZURE AD**             | Yes  | Yes    | Yes  | Yes      | Yes |
| **BMC SOFTWARE**         | No   | Yes    | Yes  | Yes      | Yes |
| **CAPTCHA**              | No   | No     | No   | No       | No  |
| **GEN AI**               | Yes  | Yes    | Yes  | Yes      | Yes |
| **GOOGLE WORKSPACE**     | Yes  | Yes    | Yes  | Yes      | Yes |
| **INFRAON PATCH**        | No   | No     | No   | Yes      | Yes |
| **INFRAON WORKFLOW API** | Yes  | Yes    | Yes  | No       | No  |
| **JAMF**                 | No   | Yes    | Yes  | Yes      | Yes |
| **JIRA**                 | Yes  | Yes    | Yes  | Yes      | Yes |
| **LDAP**                 | Yes  | Yes    | Yes  | Yes      | Yes |
| **OKTA**                 | Yes  | Yes    | Yes  | Yes      | Yes |
| **RADIUS**               | Yes  | Yes    | Yes  | Yes      | Yes |
| **RING CENTRAL**         | Yes  | Yes    | Yes  | No       | No  |
| **SERVICE NOW**          | No   | Yes    | Yes  | No       | No  |
| **SLACK**                | No   | Yes    | Yes  | No       | No  |
| **TACACS**               | Yes  | Yes    | Yes  | Yes      | Yes |
| **TEAMS**                | No   | Yes    | Yes  | No       | No  |
| **TENABLE**              | No   | Yes    | Yes  | Yes      | Yes |
| **VENDOR INTEGRATIONS**  | Yes  | Yes    | Yes  | Yes      | Yes |
| **WHATSAPP**             | No   | Yes    | Yes  | No       | No  |


---

# 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.infraon.io/infinity/user-guide/marketplace.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.