---
title: Key concepts
description: How organizations, API keys, tables, records and fields map to the Doss API.
sidebar:
  order: 3
---
## Organizations and API keys

An organization is your company's Doss account. Every API key belongs to exactly one organization and can read only that organization's data. An API key acts on behalf of the organization, not a person. It isn't limited by any user's role or user's permissions in Doss. While setting up the API key, you will need to assign the permissions for that API key (which tables the key has access to). Treat keys as privileged credentials; see [Security](/api/security).

## Tables, records and fields

The API mirrors how data is organized in the Doss app.

- **Table** in the Doss app is a **Table object** in the API. Example: Purchase Orders.
- **Row** in the Doss app is a **Record object** in the API. Example: PO-10482.
- **Column** in the Doss app is a **Field**, keyed by its API name. Example: `po_number`, `status`, `total`.

Each organization configures its own tables and fields, so two Doss instances can have different fields on a table with the same name.
