> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/oe/management-dashboard/configuring-oe-tenant/make-team.md).

# Make Team

By default there is always one team created for every Make Organization. All users initially belong to this default team. However, you can create additional teams to logically separate Make Scenarios and users according to the needs of the business. You can configure OE to point to any Make Team you want.

To set the Make Team for a tenant:

1. Go to **OE** → **Admin** → **Settings**.
2. Add the name of your Make team.

To join Make and be a member of the Make Team, the users have to be assigned to the user group that gives permissions to access Make.

<figure><img src="/files/wRvIWAJyukQmBMbVlPd2" alt="" width="456"><figcaption></figcaption></figure>


---

# 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://developer.emporix.io/oe/management-dashboard/configuring-oe-tenant/make-team.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.