Skip to content

Design your data: object types, fields and pipeline stages

Shape what Mesy stores from the Schema tab of the Admin page. Only an admin sees this tab. Every object type, field and pipeline stage in your workspace lives here.

The quickest way to add a type is a ready-made one:

  1. Open Admin, then Schema.
  2. Click Add Type.
  3. Pick a card under General CRM, Recruitment, Real Estate, Consulting, Insurance or Standalone.
  4. If the type links to other types in its bundle, Mesy lists them. Click Install with the count to add the whole set, or Only install with the type’s name to add that one.
  5. The new type appears in the Object Types list with its fields.

A card reads Already installed when a type with that name exists. Once you have a product catalogue, the product card reads A product catalog already exists in this workspace and can’t be clicked. Choose Start blank to build a type from scratch instead.

The blank form asks for a Display Name, an API Name Mesy fills in from it, and an Icon. Tick Enable pipeline (kanban board) to give the type stages from the start. A new pipeline starts with New, In Progress, Won and Lost, with Won and Lost already marked as the closing stages.

Expand a type row to reach Configuration. Semantic Role tells Mesy what the type means: Person, Organization, Opportunity, Product, Campaign or Other (no role). The role, never the name, decides what switches on:

  • An opportunity type ticked as Primary opportunity type feeds the dashboard’s pipeline metrics.
  • A product type is the catalogue the Products section searches. It needs a Price Field so line items can price from it; until then its row carries a No price field badge.
  • A campaign type gets the Marketing tab when the Marketing add-on is active.
  • A person type gets marketing consent and becomes a campaign audience, again with the Marketing add-on.

Label Field picks the field used as the record title everywhere. Visibility applies only when record sharing is on: Public (read/write), Public (read-only) or Private (owner + hierarchy).

Under Fields, click Add Field. Give it a Display Name and pick a Type. The types are Text, Number, Currency, Percent, Date, Date & Time, Checkbox, Email, Phone, URL, Select, Multi-select, Relation and Text Area. Tick Required field to refuse a record without a value. A Select or Multi-select takes its choices from Options (one per line).

A Relation field links records of this type to another type. Pick the target under Links to and tick Allow multiple links when one record may link to several. Drag a field row to reorder fields; the new order shows in tables and record pages. Fields marked System can’t be edited or deleted.

Tick Pipeline (Kanban Board) to give an existing type stages, then click Edit Stages. Type a stage in Add stage… and click Add; use Up and Dn to reorder. Renaming a stage moves every record in it to the new name in the same save. Stage names must be unique.

Removing a stage that still holds records opens Move records first. Pick a stage under Move them to and click Move and remove; the records move and the stage goes in one step. Below the editor, set Won Stage and Lost Stage (they must differ) and a numeric Value Field, or leave it as None (count only).

Under Identity Fields (duplicate detection), tick the fields that identify a duplicate, such as email or phone. A new record matching any ticked field shows a duplicate card before it’s created. With nothing ticked, the row carries a No identity fields badge and no check runs.

Deleting a field loses its data on every record. Deleting a type permanently deletes every record of that type. When records exist, the dialog asks you to type the type’s API name before Delete becomes available. System types have no delete control.