メインコンテンツへスキップ

​
Object Management

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 Twenty workspaces.
Yes, you can change the icon for both standard and custom objects in Settings → Data Model.
Not yet. Object ordering in the navigation is currently fixed, but this feature is planned for a future release.
All active objects appear in the navigation. You can deactivate objects you don’t need under Settings → Data Model.

​
Field Capabilities

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.
Our GraphQL API uses both forms for different operations:
  • createPerson (singular) for single record actions
  • createPeople (plural) for bulk operations
This creates limitations when singular and plural forms are the same, but it improves the developer experience.
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 Q1 2026. In the meantime, you can use workflows to calculate and update field values automatically.
Nested fields are coming in Q1 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.
Field reordering will be available with custom layouts in Q4 2025. Currently, fields appear in alphabetical order.

​
Relations

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 H1 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.

​
Access and Permissions

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.

​
Data Management

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.

​
Need More Help?

Check our Implementation Services for help with complex data model design.