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

# Set up the company structure

> Create Branches, Sectors and Positions before registering employees.

Before registering employees, the organization needs its **structure** created:
[Branches](/public-api/en/concepts/branch_en),
[Sectors](/public-api/en/concepts/sector_en) and
[Positions](/public-api/en/concepts/position_en). The combination of these three forms the
[hierarchy](/public-api/en/concepts/hierarchy_en) the employee will be assigned to.

<Info>
  Prerequisite: the company's `organization_id`. Find it in
  [List my organizations](/public-api/en/endpoints/organizations/public_list_my_organizations_v0_organization__get_en).
</Info>

<Steps>
  <Step title="Find the organization_id">
    List the organizations your `x-api-key` has access to and keep the `organization_id`.
  </Step>

  <Step title="Create Branches">
    Create each work site with `organization_id`, `display_name` and `cnpj`. Keep the returned
    `id` (or use `client_integration_code` to map to your system).
  </Step>

  <Step title="Create Sectors">
    Create each area/department with `organization_id`, `name` and `description`.
  </Step>

  <Step title="Create Positions">
    Create each role with `organization_id` and `name` (and `cbo`, when available).
  </Step>

  <Step title="Ready for employees">
    With Branch, Sector and Position registered, you can
    [register employees](/public-api/en/flows/employee-onboarding_en) — the hierarchy is
    resolved automatically from these three IDs.
  </Step>
</Steps>

```mermaid theme={null}
flowchart LR
    O[organization_id] --> B[POST /v0/branch]
    O --> S[POST /v0/sector]
    O --> P[POST /v0/position]
    B --> E[Ready for employees]
    S --> E
    P --> E
```

<Note>
  Use `client_integration_code` on Branches, Sectors and Positions to map each record to the
  ID in **your** system. It also works as a list filter — useful for idempotent syncs. See
  [How to use](/public-api/en/how-to-use).
</Note>