> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/white-label-documentation/install-and-configure-apps.md).

# Install and configure apps

Make's administration interface lets you install, manage, and control access to apps on your instance. In order for your end-users to access apps in their scenarios, you must first install and configure them on your instance. Your instance has only several essential tools preinstalled by default. These preinstalled tools are necessary for all scenarios to execute and include important modules like routers, iterators, and aggregators. You need to install and configure any other app you want to provide on your instance.

Managing apps requires an instance-level role such as `SA` or `Admin`. Make organizes apps into two main groups, each with its own page in the admin interface:

* **Native Apps** - The complete catalog of apps that Make develops and publishes, including enterprise and premium apps. The Native apps page lets you:
  * [Install and configure native apps](https://developers.make.com/white-label-documentation/install-and-configure-apps/native-apps.md)
  * [Configure OAuth 2.0 connections required by some apps.](https://developers.make.com/white-label-documentation/install-and-configure-apps/oauth-2.0-setup.md)
* **Custom Apps** - Private apps that you or your end-users create. You can share access to custom apps in the following ways:
  * [Via a private link to restrict access to only those who have the link.](https://developers.make.com/white-label-documentation/install-and-configure-apps/custom-apps/sharing-with-a-link.md)
  * [Via compiling the app to make the custom app available to all end-users.](https://developers.make.com/white-label-documentation/install-and-configure-apps/custom-apps/compiling-the-app.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://developers.make.com/white-label-documentation/install-and-configure-apps.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.
