> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wingup.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Organisation structure

> Split one business into branches, departments and clinics: the agent answers for the right place, and each person sees the work of their own place.

A business with more than one place, or with departments, sets up its **organisation structure** once. It stays
one business, with one agent and one list of customers. Then:

* **Each person sees the work of their own place.** A person who belongs to a branch or a department sees its
  meetings, tasks, calls and cases, and those of the units under it. They do not see the work of other units.
* **The agent answers for the right place.** A call on a branch's own number is answered for that branch, with
  its address, what it should say there, and who to transfer the caller to.
* **The app always says where you are.** The sidebar shows your unit, every list says whose work it shows, and
  every task and appointment shows its unit.

A business with one place needs none of this, and nothing changes for it.

![The organisation structure page with Haifa, Tel Aviv and the Retina clinic under Tel Aviv](https://mintcdn.com/wing-up/DHo8Bt5FFhLuKa78/images/units/structure.png?fit=max\&auto=format\&n=DHo8Bt5FFhLuKa78\&q=85\&s=a71f8e5545968277fcee32a4ae73ec14)

Settings → Organisation structure: two branches and a clinic under Tel Aviv, each with its state.

## Who it is for

The same structure fits very different businesses. Only the names and the depth change.

| Business | Its structure | What the walls do |
| - | - | - |
| A chain of clinics or shops | Branches in several cities | A branch sees its own appointments and requests. A doctor who works in two branches belongs to both. |
| A hospital or a service centre | Site → department → clinic | Each clinic sees its own work. A call centre can book for all of them and open one record when it must. |
| An association or a regulator | National office → districts → committees | A committee's cases are seen by that committee only, and by the office above it. |

A unit is a **branch**, a **department**, a **clinic**, a **site**, a **district**, a **committee** or a
**team**. A structure can be up to five levels deep.

## The pages in this part

> [card] [Setting up the structure](https://docs.wingup.ai/team/units-setup.md)
>
> Add units, put them in a tree, and choose a manager for each one.

> [card] [Who belongs where](https://docs.wingup.ai/team/units-people.md)
>
> Assign people to units one by one, from a sheet, or from your identity system.

> [card] [Who sees what](https://docs.wingup.ai/team/units-who-sees-what.md)
>
> The walls between units, and how the app shows them to each person.

> [card] [Request access](https://docs.wingup.ai/team/units-request-access.md)
>
> Open one record of another unit with a reason, for four hours. For a call centre.

> [card] [The agent in a unit](https://docs.wingup.ai/team/units-agent.md)
>
> A phone line per unit, what the agent knows and does there, and where it books.

## What is available today

| You can | Where |
| - | - |
| Build a tree of units, up to five levels, each with a kind, an address, a phone, a code and a manager | Settings → Organisation structure |
| Put a person in one unit or more, with a different role in each, and mark who manages a unit | A unit's **People** tab, or **Settings → Team and roles** |
| Bring the whole team at once from a sheet with a **Unit** column | **Import the team from a sheet** |
| Let your identity system (Okta, Microsoft Entra ID, Google Workspace) create units from its groups | SCIM, under **Settings → Team and roles** |
| Keep each unit's meetings, tasks, calls and cases inside it, closed by default | Automatic, from the first assignment |
| Open a unit to the whole business | A unit's **Details** tab |
| Choose which unit the lists show | The card at the top of the sidebar |
| Let a call centre open one record of another unit, with a reason, for four hours | A business role's **May request access to other units** |
| Download who may see what, and review every access request | The structure page |
| Give a unit its own phone number, greeting, facts, rules and transfer number for the agent | A unit's **The agent here** and **Phone line** tabs |

## What is not available yet

These are not part of the product today. Plan around them.

* **A calendar that belongs to a unit.** Appointments carry their unit, and the agent books in the unit's place,
  but each calendar is still the business's calendar or a person's own calendar. A calendar for a room, a device or
  a clinic's agenda is not available yet. The same goes for hospital scheduling systems.
* **Insights by unit.** The **Insights** page counts the whole business.
* **Automations by unit.** An automation runs for the whole business. It cannot start only for one unit.
* **Knowledge per unit.** A unit has its own facts and rules for the agent (see
  [The agent in a unit](https://docs.wingup.ai/team/units-agent.md)), but the business's knowledge base is shared by all units.
* **A WhatsApp number per unit.** A unit can have its own phone line. WhatsApp stays one number for the business.
* **Unit managers who invite people.** Only the owner invites people and changes the structure.
* **Changing the structure by talking to Wingy.** Set it up on the structure page.

## Contact support

Write to [wingy@wingup.ai](mailto:wingy@wingup.ai).


## Related topics

- [Setting up the structure](https://docs.wingup.ai/team/units-setup.md)
- [Who belongs where](https://docs.wingup.ai/team/units-people.md)
- [The calendar](https://docs.wingup.ai/bookings/calendar.md)
- [Faxes](https://docs.wingup.ai/phone/faxes.md)
- [Who sees what](https://docs.wingup.ai/team/units-who-sees-what.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.