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

# Getting Started

> Learn the basics of how data is structured and modeled in Custral.

# Overview

Custral organizes all of your customer and operational data into a unified, flexible structure.
Everything (from a single contact record to complex workflows) is built from the same core building blocks: **Objects**, **Records**, **Properties**, and **Associations**.

Understanding this structure is the key to getting the most out of your workspace.

***

## How data is structured

Custral uses a schema-driven model that mirrors how modern organizations think about their data:

| Layer            | Description                                                              | Example                           |
| ---------------- | ------------------------------------------------------------------------ | --------------------------------- |
| **Organization** | The workspace that contains all of your data, users, and configurations. | `Custral`                         |
| **Object**       | Defines a type of data, such as a person, company, or deal.              | `Contacts`, `Companies`, `Deals`  |
| **Record**       | An individual instance of an Object, a single entry of data.             | `Avery Durrant`, `Acme Corp`      |
| **Property**     | A field or attribute shared by all Records of an Object.                 | `Email`, `Status`, `Renewal Date` |
| **Field**        | The actual value stored for a Property in one Record.                    | `ada@example.com`, `Active`       |

These layers ensure that your data stays structured, consistent, and scalable across your entire organization.

***

## Relationships and hierarchy

Objects and Records don’t exist in isolation. They connect to form a complete customer or business picture.
Custral supports **Associations**, which define how data relates across Objects.

Examples:

* A **Company** has many **Contacts**
* A **Deal** is linked to one **Company** and one or more **Contacts**
* A **Ticket** belongs to both a **Customer** and a **Support Agent**

Because records link to each other, you can jump from any part of the customer lifecycle to another in one click.

***

## Why structured data matters

A consistent model means your data can power more than just storage. It can drive automation, reporting, and collaboration.

With structured data, you can:

* Filter, search, and report across any Object or Property
* Build automations and workflows triggered by specific changes
* Maintain accurate relationships between teams and systems
* Give every department the same records to work from

***

## Best practices

**1. Start with the essentials**
Define a few core Objects that represent your main data types (like Contacts and Companies).

**2. Reuse Property names**
Consistency across Objects improves searchability and analytics.

**3. Link everything through Associations**
Use relationships to keep your data connected and contextual.

**4. Revisit your model as you grow**
Your data model should evolve with your business. Add Objects and Properties as your workflows expand.

***

## Next steps

* Learn more about [Objects](/data/objects/overview)
* Explore how [Records](/data/records/overview) store your data
* Understand [Properties](/data/properties/overview) and how to define fields
* Read about [Relations](/data/properties/select/relation) to see how data connects across your workspace


## Related topics

- [Getting Started](/team/getting-started.md)
- [Introduction](/start/introduction.md)
- [Quick Start](/start/quickstart.md)
- [Workspace General Settings](/start/onboarding/workspace.md)