Schema - Data: Objects Catalog

This article provides a catalog reference of all objects available in the Neostella. Each object is classified based on whether it is system-defined and whether it supports customization. This distinction helps admins understand which objects can be extended, modified, or used as-is when designing data models.

Objects are grouped into three categories for clarity:

1. System Objects (Non-Customizable)
2. System Objects (Customizable)
3. Custom Objects (Non-System)

How to Read This Catalog

Each column in the tables below has a specific meaning:

• System Object – Indicates whether the object is native to the platform.
• Customizable – Indicates whether the object and its fields, relationships, and settings can be modified.
   

System Objects (Non-Customizable)

These core objects are essential for system operation, their structure and fields cannot be modified. Admins can reference them but cannot add fields or change relationships.

System Objects (Customizable)

The following objects are system-defined but support customization. Admins can add fields, configure relationships, and adjust settings as needed.

Custom Objects (Non-System)

These objects are fully customizable and not defined by the system. They are designed to capture specific business processes or data that extend the standard platform functionality.

The objects below are examples of fully customizable objects and are not system-defined by default. To work with any of them, admins must create and configure them using the Object Editor.