Back to Tour LibraryCore Concepts

Types

A Type defines the structure for a kind of object. Think of it as the shared blueprint for all objects of that kind.

For example, a Customer Type might define places for:

  • the customer name and status
  • contacts and account ownership
  • files and recent activity
  • related orders or projects

Consistency without rigidity

Every customer record uses the shared Customer Type, so people know where to find information and the organization can follow a consistent process.

When the business evolves, the Type can evolve too. A new field, section, or relationship can become part of the shared structure rather than being added separately to every customer.

An AnyDB Type providing structure for multiple records

One Type provides the structure used by many records.