Entity content management
Edit localized Entity titles, summaries, descriptions, images and connections so the website and AI can reference the same content.
Acceptance
Verify updated content on the website and through AI retrieval, including language variants and parent-child links.
Boundary
Entities hold facts and content. AI roles and response rules belong to prompt templates. Content editing does not imply an approval workflow or version restoration.
Set Entity relationships and reuse
[blocked]An Entity stores one item’s name and content.
Starting conditions and inputs
Identify the organization and test record.
Values for this task
entry_url, organization_id, record_id
Command sequence
Ref targets and expected results
Check the result
Source records match the criteria established for this task.
Resuming after interruption
Reread the same source IDs and resume at the unfinished check.
[blocked]Understand nodes and links
An Entity stores one item’s name and content. EntityEdge stores a parent-child link. One Entity can have several parents. Reuse it instead of copying the same fact for another placement.
[blocked]Edit links and ordering
Choose a child under the parent’s content and set its order. Each link has its own order, so the same child can appear at different positions. Cycles that lead back to the same Entity are rejected.
[blocked]Check website and AI reuse
Check both the rendered section and AI response when reusing an Entity. A graph link alone does not make every screen display it. Confirm the consumer’s reference settings and AI access scope.
[blocked]Respect relationship limits
Distinguish content relationships from purchased entitlements. Adding a link does not activate a product or grant access. Removing a link is also different from deleting the Entity itself.
Edit Entity content and translations
[blocked]Update a booking notice, edit its Korean and English text, and reopen the Entity to check both saved values.
Starting conditions and inputs
Identify one Entity and prepare approved text in each language.
Values for this task
entry_url, entity_label, description_ko, description_en
Command sequence
Ref targets and expected results
Check the result
Both translations persist. Website and AI propagation are checked separately.
Resuming after interruption
Read the same IDs again. Preserve correct settings and update only differences.
When your booking policy changes, check both your website notice and the information available to AI. Customers can receive conflicting guidance if those sources contain different rules. When several places use the same notice, find and update the Entity that holds it.
This guide explains how to edit the Korean and English descriptions of an existing Entity. The example adds a deadline to a general booking-change notice. The organization and text in the video are synthetic test data. Use your organization’s actual policy when making a real change.
Before: Contact the team to change a booking.
After: Contact the team by the day before your visit to change a booking.
First, reopen the Entity to verify the saved text in both languages. Then check the website or AI that uses it. A saved Entity is not proof that every consuming screen displays the new text.
[blocked]Decide what needs to change
An Entity holds reusable content such as service descriptions, opening hours, and booking notices. Korean and English text are separate values within the same Entity. Update the description when the factual information changes, as it does in this example.
Use prompt templates to set an AI’s tone or its response to an unknown answer. Update products and options when actual selling prices change. Editing a price explanation in an Entity does not change the price applied to a purchase.
Check your current organization before editing. If several website sections or AI accounts share the notice, confirm that the change applies to all of them. For a policy specific to one branch, check the Entity’s connections before changing shared text.
Keep a copy of the old text if you need it later. This procedure does not provide an approval history or a version-restore step.
Choose the right field
The detail panel contains an administrative name and localized text fields. To change a notice, edit Description. You do not need to create another Entity or rename the existing one.
Website sections can map these fields to different visible elements. If you want to change a heading, check which field that section displays first. Some screens use Name when Label is empty, so do not put confidential internal notes in Name.
[blocked]Edit the Korean description
1. Open the item in Content
Select Content in the left menu. Find the Entity you want to change and select its name. The video uses the Korean interface. Its 콘텐츠 menu opens the test item 문서 시험 콘텐츠. Use the corresponding item in your organization.
Read the name and existing description in the detail panel. If several items have similar names, confirm which one the website or AI uses. A matching name does not establish that two records are the same Entity.
2. Change the Korean Description field
Find the Korean input under Description. Replace the relevant sentence with your updated policy. The example uses:
예약 변경은 방문 전날까지 담당자에게 문의하세요.
This means that customers must contact the team by the day before their visit. If the description contains contact details or other instructions, preserve them. Do not replace the entire field with this example unless that is the intended edit.
3. Leave the input to save
Click another input or press Tab. The current content editor saves changes automatically when you leave the input. There is no separate Save button for this step.
Resolve any validation or save error before continuing. Even when no error appears, reopen the item at the end to verify persistence.
[blocked]Give the English description the same meaning
Check the English input under Description after editing Korean. The two inputs contain separate values, so review both. The example uses:
Contact the team by the day before your visit to change a booking.
Leave the English input to save it. If your organization does not provide English guidance, you do not need to add that language for this example.
Compare the conditions a customer will understand, rather than individual words. “Before your visit” gives a different deadline from “by the day before your visit”. Check that phone numbers, prices, times, and names also refer to the same facts.
Watch the actual editing steps
This 32-second recording edits both descriptions in a synthetic organization and reopens the Entity to verify the saved text. The interface is Korean; English captions are available. All required actions and result checks are also described in this article.
[blocked]Reopen to verify saved values and consuming screens
Reopen the same Entity
Select Close in the detail panel. Refresh the content list, then reopen the item you edited. Both description fields must retain the new sentences.
In this example, check for “방문 전날까지” in Korean and “by the day before your visit” in English. If both are present, the Entity edit has persisted. This is the result verified in the recording.
Check the website or AI that uses the content
If a website uses this Entity, reopen the page in each supported language. Check the new sentence and its layout. A longer translation must remain readable. Use website and Entity configuration to check which Entity and field the section displays.
If an AI account uses the Entity, ask the connected test channel “What is the deadline for changing my booking?”. Check whether the answer matches the new policy. For Korean, use an equivalent question such as “예약을 변경하려면 언제까지 연락해야 하나요?”
Check both the website and AI if both use the Entity. If only one uses it, check that consumer. The recording demonstrates saved Entity values; it does not verify website propagation or a live AI response.
If the result differs from what you expected
The old text returns after reopening
Confirm that you reopened the same item. If it is correct, check for errors after leaving the edited input. If the problem continues, contact support with the organization, item name, edit time, and error text. Creating more Entities makes it harder to identify the one in use.
The Entity changed, but the website did not
Check that the section displays this Entity’s Description. A section using another Entity or its Slogan will not display the edited sentence. If the connection is correct, provide the page URL and language when reporting the unchanged text.
Korean is correct, but English differs
Check that the English input retains the new sentence, then confirm the website’s current language. Verify empty-translation behavior on the consuming screen. A correct Korean page does not establish that English has been reviewed.
AI still gives the old policy
Check that the tested account references this Entity. Look for an old policy copied into its prompt template that conflicts with the updated content. Keep the actual question, answer, and test time so the cause can be investigated.