Files
twenty/packages/twenty-docs/user-guide/data-model/overview.mdx
T
Rashad Karanouh bf1220883f docs: partner CTAs on high-traffic pages (workflows, data-model, docker-compose) (#22808)
## Summary

Follow-up to #22719 (merged), which added partner-marketplace CTAs to
four **high-intent, low-traffic** docs pages (SSO, both migration
guides, implementation services).

Reviewing the docs' **top-visited pages** showed none of those four rank
in the top ~20 — they're the high-intent tail, which is correct, but
small reach. This PR extends the same pattern to three **high-traffic
pages that also carry buying intent**, without touching the pure
top-of-funnel intros/quickstarts (volume without intent → a CTA there is
just noise).

Same conventions as #22719: Mintlify-native `<Tip>` callouts,
partner-first with `contact@twenty.com` secondary, directory deep-linked
via `?categories=<scope>` and tagged with `?ref=docs-*`. No new snippet;
no `docs.json`, navigation, or translation (`l/`) changes.

## Pages changed — screenshots (one per page)

> Preview locally with `npx mintlify dev` from `packages/twenty-docs`,
or use the Mintlify PR preview once it posts. Paths below are under
`docs.twenty.com`.

### 1. `/user-guide/workflows/overview` (~593 views)
New `## Need Help?` two-bullet `<Tip>` → **Done for you** (Solutioning
partner) / **Onboarding pack** (Workflow Creation). Maps 1:1 to the
named onboarding service.

_screenshot:_
<img width="1440" height="818" alt="Screenshot 2026-07-10 at 14 34 32"
src="https://github.com/user-attachments/assets/231f681d-b5be-4b1e-9b6a-a4947a9fca37"
/>


### 2. `/user-guide/data-model/overview` (~954 views)
Replaced the plain "Need Help?" line with a two-bullet `<Tip>` → **Done
for you** (Solutioning partner) / **Onboarding pack** (Data Model
Design). Keeps the existing Implementation Services link.

_screenshot:_
<img width="1436" height="817" alt="Screenshot 2026-07-10 at 14 34 14"
src="https://github.com/user-attachments/assets/c0fe1064-1030-4062-91c7-24644ac31654"
/>


### 3. `/developers/self-host/capabilities/docker-compose` (~2421 views)
New `## Managed Hosting` single-line `<Tip>` → *find a certified Twenty
hosting partner* (Hosting), contact fallback. Framed as a lighter
"prefer not to run it yourself?" alternative — deliberately low-pressure
for the DIY self-host audience.

_screenshot:_
<img width="1437" height="815" alt="Screenshot 2026-07-10 at 14 33 39"
src="https://github.com/user-attachments/assets/a37207cd-2aaa-4aba-848d-cbf06a1e1321"
/>

## Notes for reviewers

- Page-selection rationale: intent × volume. Kept the four intent-tail
pages from #22719; added the highest-traffic pages that also carry a
natural partner-buying moment (self-host → Hosting; workflows /
data-model → Solutioning). Intros/quickstarts/contribute pages
intentionally left untouched.
- **Attribution caveat (unchanged from #22719):** twenty.com's analytics
(Cloudflare Web Analytics) is path-based, so `?ref=` is not measurable
yet. Per-page measurement via a `/go/*` redirect Worker remains a
planned, separate follow-up (out of scope here).
- `mintlify validate` passes.

Opened as a draft.


<!-- This is an auto-generated description by cubic. -->
<a
href="https://cubic.dev/pr/twentyhq/twenty/pull/22808?utm_source=github"
target="_blank" rel="noopener noreferrer"
data-no-image-dialog="true"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source
media="(prefers-color-scheme: light)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img
alt="Review in cubic"
src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a>
<!-- End of auto-generated description by cubic. -->
2026-07-10 14:39:31 +02:00

170 lines
6.2 KiB
Plaintext

---
title: Data Model
description: Learn what a data model is and how to design one that fits your business.
---
## What is a Data Model?
A data model is the structure that defines how information is organized in your CRM. Think of it as the **blueprint** of your customer data — you design it once, then fill it with your actual data.
## Key Concepts
### Objects
**Objects** are the main categories of data in your CRM. Each object represents a type of thing you want to track.
Twenty comes with standard objects:
- **People** — individuals (contacts, leads, partners)
- **Companies** — organizations
- **Opportunities** — deals or sales
- **Notes** — attached notes on records
- **Tasks** — to-dos linked to records
You can also create **custom objects** for anything specific to your business (e.g., Projects, Subscriptions, Events).
### Fields
**Fields** are the properties or attributes that describe each object. They store the actual information.
For example, the **People** object has fields like:
- Name
- Email
- Phone
- Job Title
- Company (a relation to the Companies object)
Fields have different **types**: text, number, date, select, multi-select, relation, and more. You can add custom fields to any object.
### Records
**Records** are the individual entries within an object — the actual data you create and manage.
For example:
- "John Smith" is a **record** in the People object
- "Acme Corp" is a **record** in the Companies object
**An analogy:**
| Data Model Concept | Real-World Analogy |
|-------------------|-------------------|
| **Objects** | Sections in a book (the categories) |
| **Fields** | Columns in a spreadsheet (the properties) |
| **Records** | Rows in a spreadsheet (the actual entries) |
You design the data model (objects + fields) once, then create many records within that structure.
## Why Customize Your Data Model?
Every business works differently. Customizing your data model means you can shape Twenty around **your** processes instead of forcing yours into a rigid system.
Twenty offers full flexibility:
- Create as many custom objects as you need
- Add unlimited custom fields
- The price doesn't change based on customization
## Tips to Design Your Data Model
### 1. Start with Your Core Objects
Identify the main concepts you work with. Twenty already provides:
- **People** — your contacts
- **Companies** — your accounts
- **Opportunities** — your deals
Think about what else you might need:
- Stripe would need a `Subscriptions` object
- Airbnb would need a `Trips` object
- An accelerator would need a `Batches` object
### 2. Use Fields for Variations, Not New Objects
If something is just a characteristic of an existing object, make it a **field**.
**Use fields for:**
- Categories and labels (e.g., `Industry` for Companies)
- Status values (e.g., `Stage` for Opportunities)
- Attributes and properties
### 3. Create an Object When It Stands on Its Own
If the concept has its own lifecycle, properties, or relationships, it deserves an object.
**Create an object for:**
- **Projects** — have deadlines, owners, and tasks
- **Subscriptions** — connect companies, products, and invoices
- **Events** — involve attendees and follow-up actions
These go beyond a single field because they carry their own data and relationships.
### 4. Create an Object When Records Are Open-Ended
If something can be linked multiple times and you don't know how many, use an object.
**Bad approach:**
Creating fields like `Product 1`, `Product 2`, `Product 3`...
**Good approach:**
Create a `Products` object and relate it to records. This supports one, two, or a hundred products without changing your model.
### 5. Keep It Simple First
Start with fields. Move to new objects only when you feel the limits:
- Too many fields on one object
- Repeated records that should be separate
- Relationships that don't fit neatly
## Special Note on People, Companies, and Opportunities
<Warning>
**Email and calendar sync only works with People, Companies, and Opportunities.**
These are the only objects where you can access synchronized emails and meetings from your mailbox/calendar. We recommend using them as much as possible.
</Warning>
**Best practices:**
- If you need categories of People, use fields (not new objects)
- Example: Use a `Person Type` field with values "Prospect" and "Partner" instead of creating separate objects
- Create different **views** to filter: one showing partners, another showing prospects
**It's okay to have fields that don't apply to every record.** For example, a `Referral Link` field on People that only applies when `Person Type = Partner`. Hide this field from views where it's not relevant.
## Questions to Guide Your Choice
Ask yourself:
<Check>Is this just a property of something I already have, or does it need its own properties?</Check>
<Check>Will I ever need to track multiple of these per record, without knowing how many?</Check>
<Check>Does this concept connect to several different objects, not just one?</Check>
<Check>Will it have its own lifecycle (stages, start/end dates)?</Check>
If the answer is "yes" to one or more, it's probably time for a new object.
## Accessing Your Data Model
1. Go to **Settings** in the left sidebar
2. Click **Data Model**
3. View all your objects (standard and custom)
4. Click any object to see and edit its fields
<Note>
**Don't see Data Model in Settings?**
Access to the data model is usually restricted to administrators. Contact your workspace admin if you need access.
</Note>
## Next Steps
Once you've planned your data model:
- [How to Create Custom Objects](/user-guide/data-model/how-tos/create-custom-objects)
- [How to Create Custom Fields](/user-guide/data-model/how-tos/create-custom-fields)
- [How to Create Relation Fields](/user-guide/data-model/how-tos/create-relation-fields)
## Need Help?
<Tip>
Want help designing your data model?
- **Done for you:** [find a certified Twenty partner](https://twenty.com/partners/list?categories=SOLUTIONING&ref=docs-data-model) to design and build your objects, fields, and relationships.
- **Onboarding pack:** a 4-hour guided Data Model Design session with our team — [contact@twenty.com](mailto:contact@twenty.com). See [Implementation Services](/user-guide/getting-started/capabilities/implementation-services).
</Tip>