---
id: KB-ET-007
url: https://app.codecontract.io/help/your-workspace/working-with-several-companies-or-brands
idioma: en
categoria: espacio-de-trabajo
subcategoria: cuenta
audiencia: administrador
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-ET-005, KB-AD-003]
citadoPor: [KB-ET-014]
---

# Working with several companies

_When one organisation with teams is right and when you need several._

**Responde a:** manage several legal entities in one account · separate subsidiaries or brands · one organisation or several · group of companies documentation

The question comes up as soon as there is more than one entity, subsidiary or brand. The answer turns on one thing: whether the people and the documents overlap.

| Situation | What suits |
| --- | --- |
| Several brands, same team, same suppliers | One organisation with teams |
| Different entities sharing an admin function | One organisation with teams and scoped permissions |
| Subsidiaries whose teams must not see each other | Separate organisations |
| A firm managing its clients | One organisation, one team or folder per client |

## The practical rule

Start with one organisation. Splitting later is easier than merging: moving documents between organisations is work, and splitting a history is what makes nothing add up afterwards.

> [!IMPORTANT]
> If two group entities compete or have different shareholders, separate them properly. A misconfigured permission between teams in one organisation is a configuration error; between separate organisations it cannot happen.

## What is shared and what is not

- Within one organisation: contacts, templates, balance and settings.
- Between organisations: nothing. They are independent accounts.

> [!NOTE]
> A person can belong to several organisations and switch between them without anything being mixed.

**Can a case be moved from one to another?**

It is manual work. Which is why it is worth deciding first.

**Is the balance shared?**

Within one organisation, yes. Between organisations, no.

**What about invoicing separately?**

It depends on your case; ask before building the structure.

## Ejemplos

**A group with three entities and shared administration hesitates between one account or three.**

- Sets up one organisation with a team per entity
- Scopes each team's permissions

→ Administration works across all of them and each entity sees only its own, without triplicating templates and contacts.

**Documents from two group companies get mixed.**

- Separates each company into its own organisation

→ Each one holds its own.

**One person works for two group companies.**

- Grants access to both with a single account

→ No duplicate accounts or passwords.

**A report mixes data from several companies.**

- Queries by organisation

→ Each figure belongs to whom it should.

**A client asks about the wrong company.**

- Checks which organisation holds the file

→ You answer from the right one.

**Something belonging to one company is shared from another.**

- Shares from the owning organisation

→ The trail points at the right party.