> For the complete documentation index, see [llms.txt](https://themochi-app.gitbook.io/mochi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://themochi-app.gitbook.io/mochi-docs/getting-started/set-up-organization.md).

# Set Up Organization

**Time: 1 minute**

Your organization is your workspace in Mochi. Everything — team members, leads, conversations, and settings — lives under your organization.

{% stepper %}
{% step %}

### Name Your Organization

Enter your brand or business name. This appears in your team's sidebar and helps members identify which account they're working in.

{% hint style="info" %}
**Managing multiple brands?** Each brand should have its own organization with its own Instagram connection.
{% endhint %}
{% endstep %}

{% step %}

### Upload Your Logo (Optional)

Upload your brand logo. It appears in the sidebar for all team members. You can skip this and add it later in Settings.

**Supported formats:** PNG, JPG, SVG
{% endstep %}
{% endstepper %}

### What's Next

Next, you'll connect your Instagram account — this is the core integration that makes everything work.


---

# 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://themochi-app.gitbook.io/mochi-docs/getting-started/set-up-organization.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.