Schema - Data: SETTINGS Tab Overview

  • Updated

The SETTINGS tab defines the core identity and behavior of an object through Neostella. It is where an object is anchored into the system — determining how it is identified, where it exists, how it relates to other objects, and under which context its data operates.

While objects are initially created using + NEW CUSTOM OBJECT, the SETTINGS tab is the authoritative source for reviewing and managing an object’s foundational configuration. The options defined here directly influence how the object behaves in forms, how it participates in relationships, how workflows reference it, and how other tools across the platform can access its data.

This tab also establishes context and hierarchy. By assigning an object to a specific context — such as Projects, Persons, or Organizations — admins define the scope in which records exist and how they depend on other entities. Once an object is tied to a context, its records become structurally bound to that definition, affecting how they are created, related, and reused throughout the system.

Because of this, changes made in the SETTINGS tab have a system-wide impact. They shape data structure, control dependencies, and ensure that objects behave consistently and predictably as part of the broader schema. For this reason, the SETTINGS tab plays a critical role in long-term data integrity, scalability, and governance.

In short, understanding this tab is essential for admins in charge of designing and maintaining a stable, well-structured data model.

How to Access the SETTINGS Tab

To access the SETTINGS tab:

1. Click Schema.
2. Click Data.
3. Search for an object and double-click it to open the Object Editor.
4. Select the SETTINGS tab.

8 STEPS

1. To access the SETTINGS tab.

In the Control Center, click Schema

2. Then select Data.

3. Use the Search Objects bar to find the object you want to work with.

4. Double-click it on the object.

5. This opens the Object Editor for that object. Once you’re in the Object Editor, click the SETTINGS tab to view and manage the object’s fields.

This tab may vary depending on the object type (system vs. custom).

6. This is the context object setting.

7. This is the custom object setting.

8. That's it. You have accessed to the SETTINGS tab.

https://www.iorad.com/player/2668603/Data---How-to-Access-the-SETTINGS-Tab?iframeHash=watchsteps-1&lang=en



Next step

SETTINGS Tab Dashboard

The SETTINGS tab dashboard presents all high-level configuration options that determine how the object behaves system-wide. This tab changes depending whether it is a custom or system object. The SETTINGS tab may includes: 

1. Name field
2. API Name field
3. Active toggle
4. Plural Name field
5. Creation Form field
6. Context field 		7. Link this object with a {object type} checkbox list.
8. Restrict to one per context checkbox.
9. Shared values within context checkbox
10. Allow for

19 STEPS

1. The SETTINGS tab contains the high-level configuration options that control how the object behaves across the system.

The options available in this tab may change depending on whether you’re working with a custom object or a system object.

2. For a custom object you can find the next setting tab.

3. At the top, you can find or update the Object Name.

4. Review the API Name, which is used internally by the platform.

5. The Active toggle lets you activate or deactivate the object as needed.

6. You can also define the object’s Plural Name, which determines how it appears in menus and lists.

7. Use the Context field to assign the object to a specific context within the system.

Below that, you can link the object to one or more object types by selecting the appropriate options in the Link this object with list.

8. To control data behavior, you can restrict the object to one instance per context.

9. You can enable Shared values within context to allow records to share values across the same context.

10. Finally, the Allow for setting determines which tools and areas of the platform can use this object.

11. For the SETTINGS tab. You can find the the next configuration field.

12. At the top, you can update the Object Name.

13. Review the API Name, which is used internally by the platform.

14. The Active toggle lets you activate or deactivate the object as needed

15. You can also define the object’s Plural Name, which determines how it appears in menus and lists.

16. The Creation Form setting allows you to select which form is used when new records are created.

17. Enable Shared values within context to allow records to share values across the same context.

18. Finally, the Allow for setting determines which tools and areas of the platform can use this object.

19. That's it. You have completed the settings tabs walkthrough.

https://www.iorad.com/player/2668612/Data---SETTINGS-Tab-Dashboard?iframeHash=watchsteps-1&lang=en



Next step

The options displayed in the SETTINGS tab may vary depending on the object type (system vs. custom), assigned context, and existing relationships. As a result, some objects may display additional settings or omit certain fields mentioned before.

Name Field

The Name field defines the display name of the object. This name is used throughout the user interface, including menus, forms, and references to the object.

Choosing a clear and descriptive name helps ensure consistency and usability across the platform.
 

API Name

The API Name is the system-level identifier used internally and by integrations. It is automatically generated based on the Name field using lowercase, snake_case formatting.

Once the object is created, the API Name cannot be changed, even if the display name is later updated. For this reason, the API Name should be reviewed carefully at creation time.

Active Toggle

The Active toggle controls whether the object is enabled for use.

  • Custom objects can be activated or deactivated as needed.
  • System objects are always active and cannot be disabled.

Deactivating an object removes it from active use without deleting its configuration or data, which can be useful during phased rollouts or restructuring.
 

Plural Name

The Plural Name defines how the object appears in menus, lists, and selection controls when referenced in plural form. This field improves clarity in the interface and ensures the object is presented correctly in navigation and configuration views.
 

Creation Form

The Creation Form setting determines which form is displayed when a new record is created for this object.

The selected form is based on the current object and defines the initial data entry experience, including which fields are shown and how they are organized.
 

H. Context

The Context setting defines the scope in which the object exists and operates. Context determines how records are grouped and how the object relates to other core entities in the system. Available contexts include:

  • Organizations – Represents organizations the firm works with, such as companies or institutions.
  • Persons – Represents individuals and roles within the firm or matters, such as Judges, Lawyers, Doctors, or Police Officers.
  • Projects – Represents active matters or cases, such as Criminal, Immigration, or Veteran Affairs projects.

By assigning a context, the user defines how the object’s data is structured and accessed across the platform.

The Context field does not appear for objects that already define a core context (such as Project, Person, or Organization), as these objects inherently act as the context.


Restrict to One per {Context}

The Restrict to one per {context} option limits the object to a single record within the selected context.

For example, when enabled for a Person context, only one record of this object can exist per person. This is useful for objects that represent unique or singular data points.
 

Shared Values within Context

This setting controls how relationship fields behave depending on whether the related record belongs to the same context or a different one.

When Shared values within context is enabled, the relationship field adjusts the selection flow to help users relate records more easily:

  • Within the same context, users can directly select the related record.
  • Across contexts, users first select the context record (such as a Project or Person) and then select the related child record within that context.

This approach simplifies cross-context relationships, ensures users relate records correctly, and prevents invalid associations.

Examples:

  • From a Project, selecting a Settlement from another Project requires first selecting the Project and then the Settlement.
  • From a Settlement, creating a relationship to a Pet (which belongs to a Person) requires selecting the Person first, then the Pet.

Allow For

The Allow For setting determines which tools, modules, and platform features can access and use this object. It controls the object’s availability across the platform, ensuring it is exposed only where appropriate.

Available options include:

  • Permissions.
  • Subscriptions.
  • Tags.
  • Workflows.
  • Document Generation.

For example, if an object is configured to allow for Permissions, that object becomes available in the Permission Set experience, where admins can define access rules for it. If this option is not enabled, the object will not appear when configuring permission sets.


 

Was this article helpful?

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.