Schema – Data Workspace

The Data workspace is the operational environment where admins interact directly with the data model defined in the system. 

This workspace provides a visual representation of objects and their relationships, along with the tools required to create new objects, adjust configurations, and understand how data structures connect across the system. Rather than working with abstract definitions, admins work with a living map of the firm’s data model.

Access the Data Workspace

Accessing Data is straightforward:

1. Log in to Neostella.
2. Open the Control Center.
3. Click on Schema.
4. Select Data.

Once opened, the workspace presents a dashboard that serves as the starting point for navigating objects, visualizing relationships, and managing configurations across the data model.

Here's an interactive tutorial

https://www.iorad.com/player/2667327/Data---Access-the-Data-Workspace?iframeHash=watchsteps-1&lang=en

Next step

Data Dashboard

The Data dashboard is designed to support three primary admin activities: exploration, creation, and configuration.

From this single view, admins can locate existing objects, reorganize how relationships are displayed, introduce new custom objects, and move into detailed configuration when needed. 

Here's an interactive tutorial

https://www.iorad.com/player/2667343/Data-Dashboard-Walkthrough?iframeHash=watchsteps-1&lang=en

Next step

Search Objects Bar

Search Objects Bar = the fastest entry point into the data model.

The Search Objects bar allows admins to quickly locate any object available in the system, whether it is system-defined or customizable. Selecting an object immediately surfaces it on the Data Canvas, along with its relationships and connections.

This capability is essential in environments with large or complex data models. Instead of manually navigating the canvas, admins can jump directly to an object and view it in context; making exploration faster and more precise.
 

Auto Layout Button

Auto Layout button = visual clarity at scale.

As data models grow, the number of objects and relationships displayed on the canvas increases. The Auto Layout button automatically reorganizes the Data Canvas to improve readability by recalculating spacing and object positioning.

This helps admins regain visual clarity without manually arranging elements, ensuring that relationships remain understandable even as the data model evolves.

+ NEW CUSTOM OBJECT button

+ NEW CUSTOM OBJECT button = It is an entry point to extend the data model.

The + NEW CUSTOM OBJECT button is used to introduce new customizable objects into the system. Selecting this option opens the New Custom Object builder, where the foundational identity of the object is defined.

This approach supports intentional expansion of the data model, allowing firms to add new entities only when they are clearly defined and purposeful.

New Custom Object Builder

The New Custom Object builder is the first step in creating a custom object. Its focus is deliberately narrow: establishing the object’s identity before any structural complexity is added.

Within this builder, admins define how the object will be recognized across the system, how it will be referenced by APIs and integrations, and where it will be available for use. Once created, the object becomes visible on the Data Canvas and can be expanded through fields and relationships.

By limiting configuration at this stage, the system ensures that new objects are created with clarity before being extended further.
 

Data Canvas

Data Canvas = the visual map of the data model.

The Data Canvas is the core visual workspace of the Data tool. It displays objects graphically and illustrates how they relate to one another through defined relationships. Its purpose is to provide admins with an at-a-glance understanding of how data is structured and connected.

Objects appear as visual blocks and are classified based on two attributes: Is_System and Is_Customizable.

• System Objects (Non-Customizable): Built-in objects that cannot be modified structurally in any way (for example, User).
   
• System Objects (Customizable): Built-in objects that allow extensions, such as adding fields, while preserving required system fields (for example, Project).
   
• Custom Objects (Non-System): Admin-created objects that support firm-specific data models and can be extended with fields and relationships.

While display names can be customized, all objects retain required core fields to preserve system integrity.

Relationships between Objects are represented by directional arrows. The indicators shown on these connections reflect the number of relationships defined between objects, helping admins understand the depth and complexity of each connection.

When an Object is selected on the canvas, the view updates to show its internal relationships, and the Summary Object tab opens to provide additional context.
 

Summary Object Tab

The Summary Object tab provides a consolidated, read-only view of an object’s structure and position within the data model. Its role is informational rather than configurational.

From this tab, admins can quickly understand:

• What the object represents.
• Whether it is system-defined or custom.
• Which fields are associated with it.
• How it connects to other objects.

This allows admins to orient themselves before deciding whether deeper configuration changes are required.

Context and Child Relationships

Context and Child Relationships define how Objects are contextually related to each other. Rather than establishing a strict hierarchy, these relationships determine which context an object belongs to and how it is accessed, edited, and related within the platform.

When an Object is configured with a related object context, creating a record for that object requires selecting a context (for example, Lead or Project). This context determines:

• Where the record can be accessed in the user interface.
• Which tools can interact with it.
• How it can be related to other records.

These relationships are especially important for downstream tools such as automations and workflows. Context-driven relationships ensure that actions occur in the correct scope, enabling consistent behavior across tools and supporting scalable process design without duplicating logic.
 

Object Builder

Object Builder = the source of truth for object configuration.

The Object Builder is where full configuration of customizable objects takes place. While the Data Canvas and Summary tab focus on visualization and context, the Object Builder defines how an object behaves across the system.

Through the Object Builder, admins manage fields, object types, organize them into groups, and configure object-level settings that influence how data is consumed by forms, automations, integrations, and reporting.

For teams that require precise control over their data structures, the Object Builder serves as the authoritative configuration layer.