# Standard Objects

Every Frontline account includes four pre-provisioned CRM objects. They cannot be deleted, but you can extend them with custom fields, record types, and views.

| Object | API name | Purpose | Default view |
|  --- | --- | --- | --- |
| [People](/docs/concepts/standard-objects/people) | `people` | Individual contacts | Table |
| [Companies](/docs/concepts/standard-objects/companies) | `companies` | Organizations and accounts | Table |
| [Deals](/docs/concepts/standard-objects/deals) | `deals` | Sales opportunities | Kanban grouped by Stage |
| [Tickets](/docs/concepts/standard-objects/tickets) | `tickets` | Support and service cases | Kanban grouped by Status |


## Built-in relations

- A Person can belong to one Company.
- A Deal can belong to one Company and relate to many People.
- A Ticket can belong to one Company and relate to many People.
- The reverse relations are available automatically.


These relations are already defined. Use the relation endpoints to link records; do not create duplicate relation fields.

## Built-in behavior

Standard objects include fields and automations that are not present on new custom objects:

- People are deduplicated by email and phone number.
- A Person with a business email can be linked automatically to a Company with the same domain.
- Companies can synchronize their website and domain and receive company enrichment.
- People and Companies receive communication activity and AI-generated profile context.
- Deals and Tickets track the time of their latest stage or status change.


## Extend a standard object

Standard objects support the same field, record type, view, row, activity, task, file, and export APIs as custom objects. Before adding a field, inspect the existing schema so you do not duplicate built-in behavior:

```bash
frontline object schema people
frontline object field list people
```

See [Objects](/docs/concepts/objects) for the shared API surface and [Field Types](/docs/concepts/field-types) for supported field configurations.