> 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/feature-and-settings/organization.md). # Organization Manage your workspace identity and defaults. ## Organization Name The name that appears in the sidebar and identifies your workspace. Change it anytime — it doesn't affect your Instagram connection or team invites. ## Logo Upload your brand logo. It appears in the sidebar for all team members. Supports PNG, JPG, and SVG. * Click the logo area to upload a new one * Click remove to delete the current logo ## Timezone Set your organization's timezone. This affects: * When daily digest reports are sent * Timestamp display in conversations * Dashboard date filtering ## Language Set the default language for your organization. This controls the interface language for all team members. --- # 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/feature-and-settings/organization.md?ask=&goal= ``` `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.