Docs »


Remember anything about everything

At the core of Cerb is a record management system for organizing your team’s data. A record is a distinctly identifiable entity.

Two pieces of information are needed to refer to any record:

  1. The record type (e.g. contact, organization, worker).

  2. The unique numeric identifier (“ID”) within that particular record type. IDs are automatically assigned when a new record is created.


Each record type has a set of fields to describe its attributes. Your first name and age would be two fields that describe you.

Fields types determine what type of data is stored in a field.

Field Type Description
Boolean A true or false value, represented by 1 or 0 respectively
Context A record type
Extension A plugin extension
Float A floating point number
Image A Base64-encoded images
Links A list of context:id pairs representing linked records
Number An integer (whole number)
Object A collection of keys and their associated values
Text Free-form text
Timestamp A 64-bit Unix timestamp integer, representing the number of elapsed seconds since January 1, 1970 00:00:00 GMT
URL A web page URL

Here’s what the fields for a basic worker record might look like for someone on your team:

Field Type Value
ID Number 1
First name Text Kina
Last name Text Halpue
Job title Text Support Manager
Photo File
Administrator Boolean yes
Email address Record kina@cerb.example
Mobile number Phone +1-555-123-4567
Location Text Los Angeles, California, USA
Gender Text female
Created at Date 2002-01-09 04:27:01 UTC
Updated at Date 2018-08-30 10:32:00 UTC

Custom Records

While the built-in record types cover things that every team has in common, you most likely need to keep track of data that is specific to your team and industry.

In these situations, you can easily create your own record types.

For instance:

  • If you’re a transportation company, your conversations may refer to physical trucks, planes, and ships in the real world.

  • You can link contacts to records for your products, services, licenses, and subscriptions. During support, everyone on your team will know exactly what your relationship is with each contact.

  • An educational institution can create records for students, instructors, courses, and rooms. Those records can then be linked to assets (like tablets and projectors) and support requests. If an instructor opened a support request about their projector being broken, you’d know exactly what model it is and where to find it on campus.