Objects & custom fields

Coco CRM's data model is fully customizable. Every object — standard or custom — gets its own tables, views, GraphQL API, and sidebar entry automatically. All customization happens in Settings → Data model.

Standard vs custom objects

TypeExamplesNotes
Standard objectsCompanies, People, Opportunities, Tasks, NotesShip with the platform. You can add fields to them but not delete them.
Custom objectsEmail Campaign, Lead, Lead List, Deal, Connected EmailBehave exactly like standard objects — views, API, relations, workflows all work.

Coco CRM ships with several custom objects preinstalled by the Email Campaigns app, including Email Campaign, Campaign Log, Lead, Lead List, Deal, Connected Email, and the LinkedIn/Google Places lead objects. Admins can add more at any time.

Creating a custom object

  1. Go to Settings → Data model.
  2. Click Add object.
  3. Set the singular and plural names (e.g. Contract / Contracts), an icon, and a description.
  4. Save — the object immediately appears in the sidebar with default views and is exposed through the API.

Objects can be deactivated later without deleting their data.

Creating custom fields

Open any object in Settings → Data model and click Add field. Choose a name, icon, and type:

Field typeUse for
TextFree-form short or long text
NumberIntegers or decimals (e.g. employee count)
CurrencyMoney values with a currency code
Date / Date-timeDeadlines, close dates
SelectOne value from a fixed list (e.g. Stage)
Multi-selectSeveral values from a fixed list (e.g. Tags)
BooleanTrue/false toggles
LinksOne or more URLs (website, LinkedIn)
Emails / PhonesValidated contact details
AddressStructured postal address
Rating1–5 star rating
RelationLink to records of another object

Select and multi-select fields let you define the option list, colors, and a default value. Fields can be renamed, deactivated, or deleted (custom fields only) from the same screen.

Relation fields

Relations connect objects to each other and power the linked sections on record pages:

  • One-to-many — e.g. a Company has many People; each Person has one Company. Created by adding a Relation field and choosing the target object.
  • Many-to-many — e.g. People attached to many Opportunities. Both sides show the linked records.

When you add a relation, both objects get a corresponding field automatically, and the related records appear as a section on each record page. Kanban grouping, filters, and workflows all understand relations.

Tips

  • Prefer Select fields over free text when values are enumerable — they enable kanban grouping and clean filtering in views.
  • Field API names are generated from the label; the GraphQL schema updates immediately after you save.
  • Only members whose role includes data-model settings access can modify objects and fields — see Members and Roles.