Entities
Configure your data model with custom fields, statuses, and pipelines.
Entities: the frame your data sits in
An entity describes what a record consists of. It is the first thing to exist in a new account, because everything else hangs off it: forms, lists, filters, automations and passing records to partners.
Read itFields and their types
A field is one detail on a record: phone, order value, preferred date. The type decides what may be written into it, how the value is shown and what you can filter by later.
Read itWhen the same enquiry arrives twice
The same person submits the form twice, or a source delivers a record again. You decide what the application recognises that by and what should happen then.
Read itLocations
The location module answers two questions about a record: where something lies and how big it is. There are two field types for that, the address and the area, and a map underneath both.
Read itPipelines: your process as columns
A pipeline is your way of working, written down as a row of stages. The board shows them as columns. A pipeline always belongs to one entity.
Read itVisibility: access follows responsibility
Not everyone in the account sees every record. Three things decide it: the reach of the role, the assignee, and an explicit share on the single record.
Read it