---
title: "Organization: locations, departments, positions & the chart"
description: "The company profile, the three structure tables, position permission templates, and the drag-to-rewire org chart."
---

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

# Organization: locations, departments, positions & the chart

## Company profile

Name, logo and basics. The logo uploads as soon as you pick a file, without waiting
for Save; Save in the header writes the other fields together, and stays disabled until
a field changes.

## The three structure tables

- **Locations** — the physical branches/clinics. A location is the unit of scope for
  scheduling, attendance and review. The first time a new location opens its
  [scheduling setup](/en/docs/scheduling/vocabulary/), the org template is one click
  away. Delete confirms by name.
  A location also carries its **Map Location** (**Latitude** and **Longitude**), the centre
  its [clock-in](/en/docs/time/) geofence is drawn around: click the location's row to open
  **Edit Location** and fill them in. The two are entered together or left empty together; in
  Google Maps, right-click the branch's spot and click the coordinates at the top of the menu
  to copy them, then paste into either field and they split into latitude and longitude.
- **Departments** — the horizontal cut (physicians, nursing, admin…). On the org
  chart a department is a tag, not a level.
- **Positions** — this table is **where permissions live**. One row per position with
  its permission-template badge; clicking the row opens its permissions (below), and the
  row's **Edit** button opens the position's basics, **Reports To** among them. The empty
  state states its weight: defining the first position is the prerequisite to inviting anyone.

## Position permissions

Clicking a position's row opens its permission list: what holders of this
position **can do**, one checkbox per capability, saved as a whole set by Save in the
header. People come and go, positions stay — which is why permissions hang on
positions, and [per-person overrides](/en/docs/people/) are only the exceptions tool.

A change to a position's permissions **takes effect immediately for everyone holding
it** — it is an organizational act, not a personal setting.

## The org chart

**Org chart** draws the three tables as one living picture, through two lenses:

- **Roles lens** — the reporting structure. **Drag a position card onto its new
  manager** (or onto the top-level strip) to move the reporting line — everything
  under it travels too, and a refused write snaps it back.
- **People lens** — who is at which branch. Dragging a person to another branch
  edits their assignment.

Dragging takes the matching edit permission: positions to drag a position, assignments
to drag a person. Without it you still see the chart; the cards just can't be picked up
(rather than being dragged and refused). The People lens also needs the assignments read;
without it you see the Roles lens alone.

## "Across the company" on Home

Anyone holding company-wide permissions gets an extra strip on Home — **Across the
company**: headcount (naming how many branches, where there are several), who is on
the clock right now, approvals in flight (with how long the oldest has waited), the
latest pay period, and pending claims.
Every cell is one figure that taps through to the console that answers the question
(the on-the-clock, approvals and claims cells open tabs of Company ▸ Oversight) —
the strip only states the present; anything that needs a response from you stays in
the "Needs you" list. Which cells you see follows which company-wide permissions you
hold and which modules the organization has enabled; with none, the strip is simply
absent.

Source: https://peoplematter.app/en/docs/organization/index.mdx