> 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/make-white-label.md).

# Make White Label

Explore how to navigate and administrate your White Label instance as an OEM customer.

Make’s White Label Help Center is an OEM customer’s guide to managing and administrating their white-labeled instance of Make. This documentation will walk you through administrative tasks you can perform, from rebranding the appearance of your instance to managing user access roles.

### Manage your Make White Label instance <a href="#manage-your-make-white-label-instance" id="manage-your-make-white-label-instance"></a>

Once your White Label instance has been implemented by Make and you’re ready to start managing it, you can do so in the following ways:&#x20;

* Administration interface: You can access the Administration interface by clicking **Administration** near the bottom of the left sidebar. You must have administrative access to see this button and access the Administration interface.&#x20;
* Scenarios: You can leverage the [Make modules](https://www.make.com/en/help/apps/process-management/make) and [other apps](https://www.make.com/en/help/apps) to create scenarios that help you manage your instance.

{% hint style="info" %}
You may find the [Make API documentation](/api-documentation/readme.md) to be a valuable reference for understanding and effectively utilizing the available API features.
{% endhint %}

### Administrative tasks overview

In the White Label Help Center, you'll find information about a variety of administrative tasks, including the following.

Initial onboarding tasks:

* [Installing and managing native apps](/white-label-documentation/install-and-configure-apps.md)
* [Configuring single sign-on](/white-label-documentation/manage-login/configure-single-sign-on.md)
* [Creating and managing organizations](/white-label-documentation/manage-organizations-and-teams.md)
* [Customizing your instance](/white-label-documentation/customize-your-instance.md)
* [Configuring JWT Authorization](/white-label-documentation/configure-jwt-authorization/enable-jwt-authorization.md)
* [Provisioning and managing end-user lifecycle](/white-label-documentation/manage-the-end-user-life-cycle.md)

Access and management:

* [Organizations](/white-label-documentation/manage-organizations-and-teams.md)
* [Scenarios](/white-label-documentation/audit-activity/view-recently-created-scenarios.md)
* [Recent executions](/white-label-documentation/audit-activity/access-recent-executions.md)

User roles:

* [Managing user access roles](/white-label-documentation/manage-organizations-and-teams/manage-instance-level-user-access-roles/customize-user-roles.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/make-white-label.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.