---
title: 'Edit scoped content'
description: 'Maintain local variants while preserving shared values.'
---

# Edit scoped content

A scope represents a variant such as a locale or storefront. It does not grant access. Your developer defines scopes and determines whether each field is global, local, or relationship-scoped.



## Compare two variants

1. Open a record in the default scope and save its baseline values.
2. Select a second configured scope.
3. Edit a local field, save, and compare it with the default scope.
4. Verify that global fields, such as a shared SKU, remain consistent.

A local field without an explicit value in a selected scope can use the default value. An explicit override and an inherited display can look similar; use the field's fallback/default controls when available rather than entering an empty string to guess at reset behavior.

Save or discard pending work deliberately before switching scopes. Confirm the scope in the drawer header before editing or taking a screenshot.

## Troubleshoot unexpected values

Check the attribute's scope declaration, the selected scope, and whether an override was saved. Relationship-scoped fields belong to relationship context and should be modeled using the [relationship guide](/docs/schema/relationships-and-scopes).

If the field is absent rather than showing another value, check [spaces](/docs/schema/spaces). Scope selection cannot reveal a field your membership does not permit.


---

[View full sitemap](/docs/sitemap.md)