> 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/iz-eye/anypoint-platform/configuring-connected-apps.md).
# Configuring Connected Apps
## Connected App Scopes
{% hint style="info" %}
Appropriate permissions might be required to create Connect App in Anypoint Platform.
{% endhint %}
### Creating Connected App
1. Log in to [https://anypoint.mulesoft.com](https://anypoint.mulesoft.com/)/
2. Navigate to **`Access Management`** -> **`Connected Apps`**
3. Click on **`Create App`** and select the following details
1. Name - IZ Suite Agent
2. Type - App acts on its own behalf
4. Click on **`Add Scopes`** and add the applicable scopes. Table below can be used as a reference.
5. Click on Save
6. Note the **`Client Id`** and **`Client Secret`** which will be used in the next step
### Connected App Scopes
| Job Type | Required Scope | Description .2+ |
| ------------------------------------------------- | -------------------------------------------------------- | ---------------------------------------------------------------------------- |
| Anypoint Mule Runtime Analysis | **`Read Applications`** | View Applications deployed on CloudHub |
| **`Read Runtime Fabrics`** | View Applications deployed on CloudHub 2.0 | Anypoint Exchange APIs Analysis |
| **`Exchange Viewer`** | View assets published to Exchange .4+ | Anypoint API Instance Analysis |
| **`Manage API Alerts`** | Read alerts defined for the API Instance | **`View Contracts`** |
| View contracts defined for the API Instance | **`Manage Policies`** | View policies defined for the API Instance |
| **`API Group Administrator`** | View SLA Tiers defined for the API Instance .5+ | Anypoint Sync |
| **`View Organization`** | View organizations the Connected App has access to | **`View Environment`** |
| View environments the Connected App has access to | **`View Environments in a particular organization`** | View environments the Connected App has access to in a specific organization |
| **`View Users in a particular organization`** | Required if Anypoint Teams Sync is enabled to sync users | **`Access Controls Viewer`** |
### Applying Client ID and Secret
{% hint style="danger" %}
From version 26.3.1 and above the **`Job Types`** screen is not available to the tenants. The Client Id and Secret should be updated by navigating to **`Global Settings`** -> **`Settings`** -> Search for **`Anypoint Sync Settings`** and key in the Client Id and Secret.
{% endhint %}
1. Navigate to **`Global Settings`** -> **`Job types`**
2. Search for **`Anypoint Sync`** job type and click on edit\
3. Update the value of **`Client ID`** key with the Connected App’s Client ID
4. Update the value of **`Client Secret`** key to the Connected App’s Client Secret\
5. Click on **`Ok`**
6. The **`Anypoint Sync`** scheduler will now automatically sync the appropriate Organizations/Business Groups and Environments which it has access to
### See Also
* [Aggregated Dashboard](/product-guides/integral-zone/iz-suite/iz-eye/dashboard.md)
* [Application Dashboard](/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/application-dashboard.md)
* [Agent Job Types](/product-guides/integral-zone/iz-suite/iz-core/agent/agent-job-types.md)
* [Mule Projects](/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/applications/mule-applications.md)
* [API Applications](/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/applications/exchange-apis.md)
---
# 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/iz-eye/anypoint-platform/configuring-connected-apps.md?ask=&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.
