# Managing from chat | Busymate AI Source: https://busymate.ai/docs/managing-from-chat Last modified: 2026-09-04T13:14:52+03:00 You can manage your Busymate AI workspace in the Console, or ask the signed-in assistant to do the same work in chat. Both use the same Busymate AI management tools (MCP at `https://busymate.ai/mcp`). Look-ups run right away; changes show you exactly what will change and wait for your yes; and every call stays within the workspaces your account may manage. ## Use the Console Every control this section describes lives in the visual **Console** scoped to your workspace: - **Branding** — your name, logo, colors, and welcome copy. - **Governance** — model choice (customers pick, or one default), your allowed models, and limits. See [Governance and models](https://busymate.ai/docs/governance). - **Connections** — the tools your assistant can use. See [Connecting your systems](https://busymate.ai/docs/connectors). - **Usage** — how much your assistant is used, per AI provider and over time. See [Usage and analytics](https://busymate.ai/docs/usage). - **Handoff** — turn human support on and manage the Inbox. See [Human handoff](https://busymate.ai/docs/human-handoff). Each panel is point-and-click, changes are reviewed before they publish, and everything you can touch is your workspace's — never anyone else's. ## Scoped by who you are Management is always **role-scoped**, whether from the Console or from chat: Diagram: Three levels: the platform team manages all workspaces; a workspace admin manages only their own workspace; a guest gets guidance only, no management - A **workspace admin** (you) manages your own workspace — your branding, your rules, your usage. A change to anyone else's workspace is structurally impossible for you. - The **platform team** (us) manages workspaces across the platform — creating one, verifying a domain. - A **guest** gets no management at all — just help understanding what the assistant does. Your role comes from your verified sign-in, never from anything typed in a chat, so the boundary holds no matter what's asked. ## Manage by chatting Conversational management is shipped. Ask things such as *"Show this workspace's integration status,"* *"List the content, skills, and plugins I can publish,"* *"Add this MCP connection,"* or *"Review the last 30 days of conversations."* The assistant uses the same workspace-scoped management tools the Console uses. Inside Busymate AI, a verified workspace admin or a member of the platform team gets the first-party `platform-management` connector automatically. There is no second MCP setup step in the Console and no shared application token: every call rides the signed-in person's own grant to the management address above. The contract is deliberately simple: - **Look-ups run right away.** For example, `get_tenant_integration`, `list_tenant_resources`, `list_tenant_conversations`, and `list_tenant_insights` return current workspace state. - **Changes show their payload and wait for approval.** For example, `upsert_tenant_connector` and `publish_tenant_runtime` do nothing until the signed-in admin confirms the exact action. - **A workspace admin is held to their active workspace.** A workspace id put in a prompt cannot cross that boundary, and membership is checked again when the tool runs. - **The platform team uses its verified role.** Guests get guidance only and are never given management tools. Older integrations may still call support-era names such as `upsert_tenant_support_connector` and `list_support_insights`. They still work as compatibility names, but new clients should use the product-neutral names. ## Connect from another MCP client External MCP clients connect directly to `https://busymate.ai/mcp` with OAuth 2.1 (Claude Code: `claude mcp add --transport http busymate-ai https://busymate.ai/mcp`, then `/mcp` → Authenticate). The account you connect with decides which workspaces and actions are available; putting a workspace id in a prompt or a tool argument never grants access. Keep confirmation on for changes. ### Can a workspace admin change another workspace? No. A workspace admin is held to their active workspace; a workspace id in a prompt or a tool argument never crosses that boundary. ### Are changes confirmed? Yes. A change shows its exact payload and does nothing until the signed-in admin confirms it. Look-ups run right away. ### Which MCP clients work? Any HTTP-MCP client — Claude Code, Claude Desktop, Cursor — with the URL `https://busymate.ai/mcp`. Sign-in is discovered at the address, so no extra configuration is needed. ### Is the developer-tools MCP the same server? No. The management MCP serves this product only; the developer-tools product has its own server, and neither borrows tools or credentials from the other. ## Next - **[Governance and models](https://busymate.ai/docs/governance)** — inspect or change the same rules from the Console or chat. - **[Usage and analytics](https://busymate.ai/docs/usage)** — inspect workspace usage in the Console or ask for it. - **[Getting started](https://busymate.ai/docs/getting-started)** — set up your workspace first.