> 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/native-apps/app-tiers.md).

# App tiers

Make White Label lets you designate tier levels for apps. Tiers limit access to apps so that only specific end-users can use those apps in their scenarios. For example, Make uses tiers to offer a premium level of apps reserved for **Enterprise** customers.

You can assign app tier levels by entering an integer between 0 and 3 in an app's configuration page. 0 means that the app is available to all organizations. 3 indicates the highest premium tier. Each tier level includes all apps from lower tiers. For example, tier 2 includes tier levels 0, 1, and 2.

You can then define an organization's access to premium tiers via the organization's [license object](broken://spaces/LXp8X1eBwkwrLIWrN9cg/pages/rL2Vlf2izrW74G5jDqvy).

1. Go to **Administration** > **Native Apps** > **{app}**.
2. Under **Premium app**, use the arrows to assign an integer from 0 to 3 inclusive.
3. A confirmation message briefly appears. You can now use the `premiumApps` parameter of the license object to control access.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developers.make.com/white-label-documentation/install-and-configure-apps/native-apps/app-tiers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.