# Account and workspace admin — new client, access, rename, disconnect, delete

> **You want.** *"crear una cuenta nueva para un cliente"* · *"soy agencia, cómo agrego un cliente
> nuevo / un workspace nuevo"* · *"create a new influencer workspace for a client"* · *"invitar a
> un usuario / darle acceso al cliente a Studio"* · *"invite a teammate, seats, collaborator"* ·
> *"renombrar la cuenta, cambiar el nombre del workspace"* · *"desconectar Kommo / GoHighLevel /
> HubSpot"* · *"disconnect CRM"* · *"borrar una cuenta"* · *"dónde marco un contacto de prueba,
> isTestContact"* · *"copiar un agente a otro cliente"*.
>
> **Short answer: almost none of this is an MCP tool.** Creating, renaming, sharing and deleting a
> workspace are Studio actions the operator does themselves. Do not hunt for a tool that does not
> exist: give them the exact place in Studio below, then carry on with what the MCP can do.

A **workspace** is what Studio calls a **cuenta / account** (in the agency view, a **cliente /
client**). Each one holds its own agents, contacts, connected accounts and integrations. One login
can own many; that is how agencies work.

## What the MCP can and cannot do here

| Task | MCP | Where it is done |
|---|---|---|
| Create a workspace | no | Studio (below) |
| Invite a person / give access | no | Studio → Administrar cuenta → Miembros |
| Rename a workspace | no | Studio → Administrar cuenta → Configuración |
| Delete (archive) a workspace | no | Studio → Administrar cuenta |
| Disconnect a CRM | no | Studio → Conexiones → CRM |
| Mark a contact as a test contact | no | not in Studio either — ask Ninjo support |
| Work across several workspaces | **yes** | `get_me`, then `influencer_id` on each call |
| Copy an agent into another workspace | **yes** | `create_agent` + `deploy_agent_sdk` with that `influencer_id` |

## The Studio steps, in the operator's words

**New workspace for a client.** In the sidebar account selector, click **"Nueva cuenta"**, type the
**"Nombre del cliente"** and press **"Agregar"**. Organizations can also do it from **Administrar
cuenta → "Crear cuenta"**, which needs the Owner or Admin tier. On a trial there is a cap on how many
workspaces can be created.

**Give someone access.** User menu → **"Administrar cuenta"** → **"Miembros"**.
- To add a person to the whole organization: **"Agregar miembro a la organización"** → email and tier
  (Owner, Admin, Member) → **"Enviar invitación"**.
- To give access to one workspace only: pick the workspace on the same screen → **"Agregar miembro"**
  → **"Rol"** → **"Agregar"**. **"Quitar de la cuenta"** removes it.
- Owner or Admin only. The **Equipos / Teams** screen inside Studio is for assigning conversations to teams,
  not for inviting people; that is the usual wrong turn.

**Rename.** **Administrar cuenta → "Configuración"** → pick the workspace → **"Nombre de la cuenta"**
→ **"Guardar"**. A workspace that does not belong to an organization has no rename screen: ask Ninjo
support.

**Disconnect a CRM.** **Conexiones → CRM** tab → **"Disconnect"** on the connection (Kommo, HubSpot,
GoHighLevel). WhatsApp or Instagram channels on the same account stay connected. The GoHighLevel **booking** integration is separate: **Integraciones → GoHighLevel →
"Desconectar GoHighLevel"**.

**Delete a workspace.** **Administrar cuenta** → trash icon **"Eliminar cuenta"** (or Configuración →
**"Zona de peligro"**), then type the account name to confirm. It archives rather than erases: access
and channels are removed, the data is kept, and an administrator can restore it. **"Mover fuera"**
only takes a workspace out of an organization, without deleting it.

## Working across workspaces through the MCP

1. `get_me` — returns the connection's scope and `available_influencer_ids`, with the handle of each.
2. Pass `influencer_id` on every call that should act on a workspace other than the default. With a
   multi-workspace connection and no default, it is required, and the call fails without it.
3. A connection authorized for one workspace only sees that one. To reach a workspace created after
   connecting, reconnect (`/mcp`) and pick it, or authorize the whole portfolio.

**Copying an agent to another client** is `create_agent` in the target `influencer_id`, then a full
first `deploy_agent_sdk` (all 8 v5Config fields), then its triggers. Agents cannot be moved between
workspaces, and CUSTOM tools do not travel with them: re-register them in the target. Full sequence:
`knowledge/sdk-migration-playbook` §11–12.

## How it goes wrong

- **A new workspace is invisible to Claude.** The MCP connection was authorized before the workspace
  existed, or for a single workspace. `get_me` will not list it. Reconnect; nothing is broken.
- **"Invited" but the person sees nothing.** They were added to the organization but not granted the
  workspace, or the other way round. Check both on the Miembros screen.
- **Disconnecting did not stop the agent.** It only cuts the connection, not the agent. To
  stop an agent answering, `set_agent_status`; to stop one contact, a contact limit.

## See also

- `knowledge/connecting-integrations` — connecting (not disconnecting) integrations and calendars,
  `create_connect_link`.
- `knowledge/messaging-channels` — which number or account an agent answers on.
- `knowledge/how-to/multi-agent-routing` — several agents in ONE workspace, the question people often
  mean when they ask for a second workspace.