Data Model FAQ

Yes, custom objects can be deleted. You can also deactivate them first, which hides the object and its data from the interface while preserving the data.

No, standard objects cannot be deleted. You can only deactivate them, which hides them from the interface but preserves the data.

You can create as many custom objects and fields as you need — the price doesn't change.

You can rename the label of standard objects (People, Companies, Opportunities), but not their API names. The API names are fixed for consistency across all Grovana workspaces.

Yes, you can change the icon for both standard and custom objects in Settings → Data Model.

Yes. With the Layouts permission, enter sidebar customization mode to drag and drop items in the Workspace section. This order is shared across the workspace. Items in Favorites are personal to each user and can be reordered without entering customization mode. See the Sidebar guide.

You can hide objects you don't use from the sidebar without deleting them. You can show them again from Settings → Data Model. See the Sidebar guide.

No, field types cannot be changed after creation. If you need a different type, create a new field with the correct type, migrate your data, then deactivate the old field.

Grovana needs distinct names for a single record and a group of records. For example, use "Person" and "People".

Certain field names like Type or Application are reserved for system use. Choose alternative names like Category or Classification instead.

• The field is hidden from the interface
• Existing data is preserved
• You can still access the field via API
• Existing relations remain but you can't create new ones
• You can reactivate the field later

Currently, you cannot make custom fields required. All fields accept empty values. You can use workflows to enforce required fields by sending alerts or blocking actions when fields are empty.

• Unique: No two records can have the same value in this field
• Required: The field must have a value (not currently supported for custom fields)

Formula fields are coming in H2 2026. In the meantime, you can use workflows to calculate and update field values automatically.

Nested fields are coming in H2 2026. Currently, you can use workflows to bring field values from related objects. For example, to display a company's industry on a Person record, create a custom field on People and use a workflow to synchronize the value.

Yes, go to Settings → Data model → object of your choice → Layout and click Customize record page. If this button is disabled, you must create a record.

Yes! Self-referencing relations are supported and recommended for use cases like account hierarchies. For example, create a relation from Companies to Companies to track parent/child accounts.

Many-to-many relationships are coming in H2 2026. Currently, create an intermediate object with two one-to-many relationships as a workaround.

For example, to link People and Projects (many-to-many), create a "Project Assignments" object with:

• A relation to People (many assignments → one person)
• A relation to Projects (many assignments → one project)

These allow one object to relate to multiple different object types through a single field. For example, Notes can be attached to People AND Companies AND Opportunities simultaneously.

Each Note links to one Person, one Company, and one Opportunity at the same time.

Learn more in Relation Fields.

Yes, you can create multiple relations between the same two objects. For example, a Company could have both a "Primary Contact" and "Billing Contact" relation to People.

When you delete a record, the relation link is removed from the related records. The related records themselves are not deleted.

While technically possible, circular relations (A → B → C → A) should be avoided as they can cause confusion and potential performance issues.

Go to Settings → Data Model to view and edit all your objects and fields.

Reach out to your workspace administrator. Data model access is usually restricted to administrators only.

There's no hard limit on record counts. However, very large datasets may impact performance in some views. Use filters and views to manage large datasets effectively.

Yes, you can import CSV data into any object, including custom objects. The import process supports field mapping for custom fields. See How to Prepare Your CSV Files.

Currently, there's no built-in export for data model configuration. Contact support if you need to migrate your data model between workspaces.

The maximum number of fields a single object can have is 1600 fields as per Postgres limits, including both existing and deleted fields. Be aware that Grovana won't fix your workspace if the limit of 1600 fields is reached as it falls under our Fair Usage policy.