---
title: "Entities: Resolving a type's fields using multiple subgraphs"
canonical: "https://support.apollographql.com/space/ETKB/626294844/Entities%3A%20Resolving%20a%20type's%20fields%20using%20multiple%20subgraphs"
format: markdown
---
Resolving types across multiple subgraphs can refer to a few different scenarios, depending on what you need to accomplish.

If different subgraphs will contribute different fields to the same type, you create an [entity](https://www.apollographql.com/docs/federation/entities/). If a subgraph defines an entity, it can do any of the following:

- [Contribute fields to the entity directly](https://www.apollographql.com/docs/federation/entities/#contributing-entity-fields)
- [Compute field values based on the values of ](https://www.apollographql.com/docs/federation/entities-advanced#contributing-computed-entity-fields)*[other](https://www.apollographql.com/docs/federation/entities-advanced#contributing-computed-entity-fields)*[ entity fields](https://www.apollographql.com/docs/federation/entities-advanced#contributing-computed-entity-fields)
- [Define the entity without contributing any fields at all](https://www.apollographql.com/docs/federation/entities/#referencing-an-entity-without-contributing-fields)

If different subgraphs will resolve the *same* fields of a type, you use the `@shareable` directive to enable this behavior.

If an object field will move from one subgraph to another, you use the `@override` directive to indicate that the field is now resolved by this subgraph instead of another subgraph where it's also defined.