Overview

Editing a domain is not just about changing a label. In many cases, that review affects other lists, forms, integrations or components that depend on the same structure. Because of that, this area should be maintained with a functional reading, not only a visual one.

Structural review
Functional impact
Governance

1

What is worth reviewing in a domain

Read before editing

Naming

The internal name and language-specific names should remain clear for the team and coherent with the actual purpose of the list.

Technical fields

Codes, webservices, statuses and structural relationships should be reviewed whenever the project logic changes.

Associated values

It is also important to confirm whether list items are still valid, whether duplicates exist and whether the structure still makes sense.

2

Edit the main domain structure

Reopen the base entity

Domain editing form in Studio CMS
The same structural base used during creation can be reviewed later to adjust names, relationships, statuses and integration fields as the project evolves.
  • Update internal names or language-specific names only when the change improves the functional reading of the list.
  • Review technical codes and integrations when the data source or the operational logic of the domain changes.
  • Confirm the active/inactive status so the structure is only exposed when it is ready for real use.
  • If there is a parent domain, validate whether the relationship still matches the current project structure.
Best practice: before saving structural changes, align the update with the team that uses the domain daily so the structure does not become ambiguous.
3

Manage the associated values

Add, review and clean items

Associated domain values listing in Studio CMS
The values area contains the finer management layer of the list: item creation, language review, status maintenance and cleanup of what is no longer needed.

Add or correct

When new options enter the process, you can add values or correct names that no longer reflect the current functional reality.

Remove or consolidate

If there are repeated or obsolete items, maintenance should simplify the list without compromising existing dependencies.

4

Validate impact before saving

Critical maintenance step

1. Confirm where the list is used

Before editing, try to understand whether the domain is linked to forms, filters, integrations or other structures already in production.

2. Validate impact on values

A small change in a name, status or relationship can affect list behavior in other parts of the system.

3. Save only when the impact is clear

When the impact is still unclear, the safest next step is usually to align first with the functional or technical team.

Attention: a domain may look like just a list, but it often supports silent dependencies. Poorly assessed changes can create inconsistencies that only appear later on the website or inside integrations.
5

Explore also

Related content for this maintenance flow

Domain concept

Return to the base structure logic if you need to confirm the role of the domain before reviewing names, statuses or relationships.

Create a new domain and manage values

Review the initial setup to separate what belongs to the base creation flow from what belongs to ongoing maintenance.

Filemanager

Just like domains, this area also benefits from organization and ongoing maintenance to keep the project healthy.

FAQs

Check broader Studio questions when you need additional context before changing shared structures.