The FIELDS tab is where admins define, configure, and manage all fields that belong to an object. Fields are the atomic data points that store information, and everything users enter through forms, automations, and processes originates here.
This tab centralizes field creation, organization, filtering, and configuration. It allows admins to control how data behaves, who can interact with it, and in which contexts it is available. The FIELDS tab plays a foundational role in shaping how object data is consumed across the platform.
How to Access the FIELDS Tab
To access the FIELDS tab:
1. Click Schema.
2. Click Data.
3. Search for an object and double-click it on the Data Canvas.
The Object Editor opens.
4. Click the FIELDS tab.
Here's an interactive tutorial
FIELDS Tab Dashboard
The Field tab dashboard is designed around two primary configuration areas:
1. Fields Menu - Used to manage, search, filter, and control the visibility of fields.
2. Field Setup Panel - Used to configure the properties and behavior of an individual field.
Together, these areas allow admins to efficiently manage large numbers of fields while maintaining precise control over field behavior.
Field Menu
The Field Menu provides high-level management tools for all fields associated with the object. From this menu, admins can add new fields, locate existing ones, and apply filters based on visibility or limitations. The Field Menu includes:
|
1. + New button 2. Search bar 3. Locked button 4. Hidden button |
5. Archived button 6. Field filter button 7. Object’s fields list |
Here's an interactive tutorial
+ New Button
The + New button is used to add a new field to the current object. Selecting this option opens the Field Setup Panel, where the field’s configuration is defined.
Search Bar
The Search bar allows admins to filter existing fields by name. This is especially useful when working with objects that contain a large number of fields.
Limitation Filter Buttons
Field limitations can be filtered using three dedicated buttons. These buttons directly reflect the Limitations settings configured in the Field Setup Panel.
- Locked – Displays fields that are marked as locked and cannot be edited.
- Hidden – Displays fields that are marked as hidden and are not visible to end users.
- Archived – Displays fields that are archived and no longer active.
These filters help admins quickly audit field status and manage field visibility and availability across the object.
Field Filter Button
When an Object contains many fields, the field filter button allows admins to narrow results using multiple criteria, including:
- Field Type - Email, number, date.
- Field Group - Groups created in the Field Groups tab.
- Limitations - Locked, Hidden, Archived, or Sali Tag.
Filters apply immediately and help surface only the most relevant fields.
Object’s Fields List
This list displays all fields that currently belong to the object. Selecting a field opens its configuration in the Field Setup Panel.
Field Setup Panel
The Field Setup Panel is where detailed configuration for each field can be found. Depending on the selected field type, the options displayed here change dynamically but all fields follow the same core configuration structure.
|
1. Field Name
4. Limitations dropdown |
6. Field Groups dropdown 7. Sali Tag 8. Required checkbox 9. Include In Quick Search checkbox 10. Restrict to {Object} Types list |
Here's an interactive tutorial
Field Name
The field Name defines the display name of the field. This value can be edited at any time and automatically serves as the basis for the API Name field.
Field name rules:
- Cannot add the next special characters: ‘-’ or ‘_’.
- Cannot include system-reserved words (such as list, type, object-type, object context, field).
- Must contain at least 3 characters.
Field API Name
The API Name field is an informational, system-generated value derived from the Field Name.
Field Type
The Field Type determines how the field behaves, how it appears in forms, and how data is stored and validated. Below are the supported field types:
| Field Type | Field Type Options | Definition | How It Works |
| Emails | List | A field used to store a valid email address. It typically checks for proper formatting (example@neostella.com). |
Field: Add Email Type Value entered: client@lawfirm.com The system validates the format before saving. |
| URLs | List | A field for adding website links. Automatically validates standard URL formats. |
Field: Firm Website Value entered: https://www.neostella.com |
| Address | List | A structured field for capturing physical location details such as street, city, state, and ZIP/postal code. | The Address field stores multiple related values, including street address, city, state, ZIP/postal code, and country. Some subfields support searchable single-select lists and format validation. Admins can configure which address components are visible and required. |
| Phone | List | A field designed to store telephone numbers. Often includes country code and basic formatting checks. |
Field: Add Phone Type Value entered: +1 (305) 555-9876 |
| Text |
Text TextLarge |
A flexible field that stores written information. Can hold short or long-form text depending on configuration. |
Field: Case Description Value entered: “Client reported an incident on June 5th involving…” |
| Numbers |
Decimal Integrer Percentage Currency |
A numeric-only field for storing quantities, values, or calculations (e.g., counts, IDs, budgets). |
Field: Settlement Amount Type: Currency Value entered: $25,000 |
| Date | None | A field for selecting or entering a specific calendar date. |
Field: Case Start Date Value selected: 15/03/2025 |
| Yes / No | None | A binary field type that captures a simple true/false or yes/no answer. |
Field: Documents Received Value selected: Yes |
| Deadline | None | A date-based field used specifically to track due dates or target completion dates. |
Field: Filing Deadline Value selected: 04/01/2025 |
| Dropdown | None | A field that lets users select one value from a predefined list of options. |
Format example: - Roles Intake Specialist Case Manger Medical Record Requester Options: Intake Specialist Case Manger Medical Record Requester |
| Multi-select | None | A field that allows users to choose multiple options from a predefined list. |
Format example: - Skills Excel Power BI Word Options: IExcel Power BI Word |
| Radio Button | None | A field that presents several options, but only one can be selected at a time (similar to a dropdown but visually displayed). |
Format example: - Priority High Medium Low Options: High Medium Low |
| Relationship | List | A field used to link records or objects together—for example, connecting an object to another object. |
Field: Related Client Value selected: John Smith (Contact object) |
| Merged Field | None | A read-only field that combines two or more existing fields into one display value (e.g., “First Name” + “Last Name”). |
Format example: Selectors Used: {{apiname.first_name}} {{apiname.last_name}} Complete: - Full Name {{apiname.first_name}} {{apiname.last_name}} |
| Period | None | A field used to define a period of time or duration, representing how long an exposure or condition applies. |
Field: Reporting Period Value selected: Q2 2025 |
For example, when selecting the Text field type, it can be chosen between Text and Large Text. Depending on the option selected, additional configurations may become available — such as enabling the field as a List.
For example, if an Email field is set as a List, a single record can contain multiple email addresses. This allows the system to store all relevant values for that field without creating separate records or duplicate fields.
Using the List option helps keep data structured and complete while supporting real-world scenarios where more than one value is needed.
Each field type introduces its own configuration rules and behaviors, but all integrate consistently across the platform.
Limitations
Field Limitations control how fields behave across forms, APIs, and the underlying object schema. They allow admins to define what users can see, edit, or interact with, without changing the field’s type or structure.
There are three available field limitations:
- Locked – The field remains visible but is read-only. Users can view the value, and it is returned in API GET requests, but it cannot be edited through the UI or updated via PUT requests.
- Hidden – The field is removed from user-facing forms and is not visible to end users. Existing values cannot be viewed or modified through the UI. The field remains part of the object schema and can still be used by system processes, automations, or logic.
- Archived – The field is no longer active or visible in standard views. It cannot be edited or populated, but it remains stored in the schema for historical or structural purposes and can be restored if needed.
Each limitation affects field visibility and editability differently depending on whether the interaction occurs at the form, data, or schema level. Admins can review and manage these states using the Field menu filters.
Custom Permissions
The Custom Permissions setting allows admins to assign predefined permission sets to a field.
Permission sets are created under: Access → Permission Sets, where custom permissions are defined. These permissions control which users can view or edit specific fields.
Field Groups
The field groups setting assigns a field to one or more groups created in the FIELD GROUPS tab. Field Groups act as labels that improve organization and filtering within the FIELDS tab or forms.
Sali Tags
Sali Tags provide a standardized tagging schema that unifies how information is classified across different firms and systems.
Instead of each firm using its own terminology or category structure — for example, one firm using a category named ‘Artifacts’ and another using ‘Documents’ — Sali Tags allow both to reference the same underlying concept, such as ‘Document Artifact’, using a shared taxonomy.
This creates a layer of homogeneity and best practices in the backend, regardless of how each firm chooses to name or organize things in their own configuration. Sali Tags rely on a hierarchical structure, allowing concepts to be grouped and related in a consistent, scalable way.
Required Checkbox
When enabled, the Required checkbox enforces that the field must contain a value at the API level.
Include in Quick Search
When enabled, this option prioritizes the field in quick search operations, making it easier to locate records. Selecting multiple fields as quick searchable will impact the search performance.
Restrict to Object Types
This setting controls which Object Types the field applies to, based on the structure defined in the Field Types tab.
- If no types are selected, the field is available for all Object Types.
- If specific types are selected, the field is only available for those types.
This option is critical because it directly impacts how Fields are presented to end users and ensures that data appears only in relevant contexts.
For example, an object includes two types: ‘Lead’ and ‘Project’. A field named ‘Estimated Case Value’ is restricted to the project type. As a result, this field appears only when viewing or editing Project records and is not shown for Lead records.
Comments
0 comments
Please sign in to leave a comment.