> For the complete documentation index, see [llms.txt](https://help.accentuate.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.accentuate.io/metafield-definitions/create-a-metafield-definition/label-and-namespace.md).
# Label & Namespace
### What is a label in Metafields?
**Label** - internal identifier you’ll see inside the app to help you stay organized.
**Name / Key** - automatically generated based on the label, but you can also edit it if you want.
### What is a namespace?
In Shopify Metafields, a **namespace** works together with a **key** to define and organize custom fields. Think of it as a way to group and separate your fields so they don’t clash with fields from other apps.
By default, Accentuate uses the **accentuate** namespace to keep your Metafields organized and separate. That’s why setting a namespace is optional, unless you have a specific reason to customize it, **Accentuate takes care of it for you.** However, you can override this and set your own namespace for any individual field if needed.
It is also a great way to (technically) group sets of fields that naturally belong together. For instance:
* Use `image.title` and `image.rating` for image-related fields
* Use `video.title` and `video.rating` to group video-related fields
If you need to use ACF to manage Metafields created from other apps, you can match the namespace and key for the fields when defining the field type and ACF will automatically use any existing values going forward. Just take care to define a field type that makes sense with regard to any existing data.
{% hint style="info" %}
Some namespaces are reserved for internal ACF use and cannot be used for field definitions. The field definition dialog will not allow you to define fields using the namespaces *acf\_settings, product\_types, vendors, locations* or *globals*
{% endhint %}