> For the complete documentation index, see [llms.txt](https://docs.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.icustomer.ai/settings/workspace-and-brand.md). # Workspace and brand Your workspace: what it holds, who can change it, and how many you can have. A workspace is your environment: one company or brand, with its own data, context, team, and settings. Everything the system knows and does lives inside it. ## Workspace details Under **Settings → Workspace** you can rename the workspace. Only the owner and admins can edit workspace details. Your brand itself, what you sound like, who you compete with, how the system stays on-brand, is not a settings form. It lives in your working context, built during onboarding and refreshed as the system learns. You edit it by talking to iHarness, not by filling in fields. ## How many workspaces Each workspace maps to one brand or business unit. The number of workspaces you can own follows your plan: one on Free and Pro, three on Team, and as many as you need on Enterprise. Members you invite join a workspace; owners see all of their workspaces under one subscription and one credit pool. See [Billing](/settings/billing.md). ## Outside the app Workspace details can be read outside the app via [API](/settings/api-keys.md) and [MCP](/iharness/bring-your-own-agent.md) as well. --- # 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://docs.icustomer.ai/settings/workspace-and-brand.md?ask=&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.