# organizations (/product/modules/organizations)



`organizations` is the master party table. A customer, a supplier, an employer, a creditor and a financial services provider are all rows here, told apart by type; a referencing table keeps its semantic name, so an order's customer and a price's supplier both point at this table.

## Owns

| Table           | Holds                                                                                               |
| --------------- | --------------------------------------------------------------------------------------------------- |
| `organizations` | The party: registration, contact, industry, country, currency, and a parent pointer.                |
| `locations`     | A place an organization owns, stores and warehouses, typed, with coordinates and a geofence radius. |

The parent pointer makes it a tree. In the field solution that tree is the whole structure, national to region to area to store, with an **organization level** naming each depth as a tenant-authored lookup; a store is a leaf, and the field agent's check-in is measured against the store's location geofence.

## Routes

`/organizations`: the grid and form, with locations nested.

## Settings scope

`organizations`.

## Permissions

`organizations.manage`. Reads are open to every signed-in user, and a rep may create the organizations they work with, the one owner-write exception in the protected tier.

## Switched off

Never. Every project links it at provisioning.