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:
The record type (e.g. contact, organization, worker).
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.
|Boolean||A true or false value, represented by
|Context||A record type|
|Extension||A plugin extension|
|Float||A floating point number|
|Image||A Base64-encoded images|
|Links||A list of
|Number||An integer (whole number)|
|Object||A collection of keys and their associated values|
|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:
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.
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.