--- title: "[Fields] - Reference" description: Reference field documentation for linking entries across the same or different content types. url: https://www.contentstack.com/docs/developers/create-content-types/reference product: Contentstack doc_type: reference audience: - developers - content-managers version: unknown last_updated: 2026-03-25 --- # [Fields] - Reference This page explains the **Reference** field, how it links entries within the same or different content types, and the related configuration options and behaviors. It is intended for developers and content modelers designing content types, and for content managers who work with referenced entries while creating and editing content. ## Reference The **Reference** field lets you link entries from the same or different content types. It enables structured relationships between content and allows you to reuse entries across your stack. You can update the following properties of a Reference field at any time: - [Display Name](/docs/developers/create-content-types/display-name) - [Unique ID](/docs/developers/create-content-types/unique-id) - [Placeholder Value](/docs/developers/create-content-types/placeholder-value) - [Instruction Value](/docs/developers/create-content-types/instruction-value) - [Help Text](/docs/developers/create-content-types/help-text) - [Multiple](/docs/developers/create-content-types/multiple) - [Mandatory](/docs/developers/create-content-types/mandatory) - [Referenced Content Type](/docs/developers/create-content-types/referenced-content-type) **Additional Resource**: - Use [Field Visibility Rules](/docs/developers/create-content-types/about-field-visibility-rules) to hide or show fields based on conditions. - Refer to [Reference vs Select vs Tags](/docs/developers/how-to-guides/reference-field-vs-select-field-vs-tags-field) fields to understand field differences. Creating references within the same content type is known as **Self Referencing**, while referencing other content type(s) is known as **Include Referencing**. Let’s explore them in detail. ## Self Referencing Self Referencing allows you to reference entries from the same content type. For example, in an e-commerce application with content types such as **Category**, **Brand**, and **Product**, you may want to recommend related products. You can add a Reference field within the **Product** content type that references other **Product** entries. To configure: - Add a **Reference** field to the Product content type. - Rename it (for example, *Recommendations*). - Select **Product** as the referenced content type. Content managers can then select related products when creating or editing entries. ## Include Referencing Include Referencing allows you to reference entries from one or more different content types. There are two approaches: - ### Single Content Type Referencing Allows referencing entries from one specific content type. If you have **News Article** and **Author** content types, you can add a Reference field in News Article that references Author entries. To configure: Add a Reference field to the **News Article** content type. - Rename it (for example, *Author Details*). - Select **Author** as the referenced content type. Content managers can then select one or more authors while creating news articles. - ### Multiple Content Type Referencing Allows referencing entries from multiple content types. If you have content types such as **Clothes**, **Shoes**, and **Bags**, and want to associate them with a **Brand**, you can: Add a Reference field to the **Brand** content type. - Select multiple content types under **Referenced Content Type**. - Enable the **Multiple** option. Content managers can then select entries from all configured content types. **Note**: You can add up to 50 content types in a single Reference field. Refer to the **Limitations** section for details. ## Additional Functionalities The Reference field includes several features to help manage relationships effectively. ### View Reference Map The **View Reference Map** feature visualizes relationships between entries. When an entry references other entries, or is referenced by them, the **View Reference Map** option appears in the entry editor’s **Information** panel. Selecting this option opens a modal displaying a visual map of relationships. #### How It Works - The **left side** shows parent entries (entries that reference the current entry). - The **right side** shows child entries (entries referenced by the current entry). - The map initially loads direct parents and children. - You can expand nodes to explore deeper relationships. - Clicking an entry opens it in a new browser tab. - The interface supports zooming, panning, and dragging. This feature helps you understand complex content structures at a glance. ### Creating New Entries from Reference Fields You can create new entries directly from a Reference field without leaving the entry editor. **Note**: The **Create new entry** option is available only if the *Save In Progress Entry* feature is enabled in your plan. ### Navigate Using Breadcrumbs Use breadcrumbs within nested references to move between related entries easily. This is especially useful when managing complex content structures. ### Edit Referenced Entries After selecting a reference: - Click the **Edit** icon next to the referenced entry. - The entry opens for editing. **Warning**: Save the parent entry before navigating away to avoid losing unsaved changes. ### Add Multiple References If the field is configured as **Multiple**, you can: - Select existing entries - Create new entries When selecting entries: - Use the **Select content type** dropdown (if multiple types are configured). - Click **Add selected entries**. **Note**: If a referenced child entry is deleted, only its UID and content type UID remain visible. ### Permissions on Referenced Content Types Permissions determine how users interact with referenced content types. #### Scenario 1: No Read Access If a user does not have **Read** access to the referenced content type: - They cannot view entries in the Reference field. - Saving the entry results in no reference data. - Editing and saving removes previously set references. #### Scenario 2: Read Access but No Publish Access If a user has **Read** access but not **Publish** access: - They can select referenced entries. - They cannot publish the parent entry. The Reference field enables structured content relationships across your stack, allowing you to build reusable, connected content models. By linking entries within or across content types, you can create scalable architectures that support dynamic content delivery and efficient content management. ## Common questions ### What is the difference between Self Referencing and Include Referencing? Self Referencing allows you to reference entries from the same content type, while Include Referencing allows you to reference entries from one or more different content types. ### How many content types can be added to a single Reference field? You can add up to 50 content types in a single Reference field. ### Why can’t a user see or save references in a Reference field? If a user does not have **Read** access to the referenced content type, they cannot view entries in the Reference field, saving the entry results in no reference data, and editing and saving removes previously set references. ### When is the “Create new entry” option available in a Reference field? The **Create new entry** option is available only if the *Save In Progress Entry* feature is enabled in your plan.