Content Operations
Prepare publishing, forms, media, community, and event workflows for launch.
Content Operations
Use this page for non-commerce areas that need operators before launch: publishing, forms, media, community, and events.
Publishing And Content Locales
Use the active workspace and your assigned tenant-admin or tenant-editor role for permitted edits; tenant-viewer is read-only. Collection-specific actions can require a higher role. For app implementation, use the Events and Community task guides; they do not replace cancellation, moderation, or launch procedures here.
Articles and products have localized editorial fields. A tenant-admin or super-admin configures the workspace's enabled content locales, default locale, and fallback. Admin Panel UI language is independent of content locale. Edit one enabled content locale at a time; an explicitly disabled locale is rejected. When fallback is enabled, missing localized values use the workspace default locale; disabling fallback does not create a translation.
For these localized collections, status, publishedAt, and slug are shared across locales. Publishing or archiving applies to all locales at once; a translation has no separate publication state. Public visibility also follows each collection's publication/access rules. Review the public result in each enabled locale before launch. Hiding an Admin Panel field or changing a menu label does not change publication or API permissions.
Empty tab guidance
When field visibility settings hide all content in a tab, the tab shows guidance and a Field visibility settings link. Select the fields you need and save to show the content again. Tabs with visible inputs, descriptions or UI continue to show that content.
Content Areas
| Area | Ready when | Owner to name |
|---|---|---|
| articles | at least one publishable article and author process exist | publishing owner |
| documents | document types and first live document are ready | knowledge owner |
| forms | one active form exists and submissions are monitored | response owner |
| galleries, videos, playlists, links | first media or link set exists with review ownership | media owner |
| community | starter categories, reaction types, and moderation owner exist | moderation owner |
| events | event owner, calendar ownership, event details, and occurrence updates are assigned | events owner |
Document Metadata Visibility
In the Console field visibility overview, open Documents to show or hide Keywords, Jurisdiction, Language, and Superseded by. Keywords controls the entire keyword list. Save your choices, then select and save them again to show the fields. These fields remain visible until you choose to hide them; existing visibility settings are preserved. Hiding affects the Admin Panel only and keeps stored values and API access unchanged.
Image Placeholders
The read-only LQIP field on images, brand logos, and workspace logos shows a small image placeholder and its description. When no value is available, it shows No LQIP in English or LQIP 없음 in Korean, following the Admin Panel language. You can select and copy an existing value from the text input.
Link Option Visibility
In the Console field visibility overview, open Links to show or hide Platform, Open in new tab, and Expires at. Save your choices, then select and save them again to show the fields. These fields remain visible until you choose to hide them; existing visibility settings are preserved. Hiding affects the Admin Panel only and keeps stored values and API access unchanged. Hiding Expires at still excludes the link from storefront lists at its stored expiry time.
Link URL Errors
When saving a link in the Admin Panel, errors for a missing URL, an invalid address, or an unsupported protocol use your selected Admin language. Correct the URL before saving again.
Gallery Layout Visibility
In the Console field visibility overview, open Galleries to show or hide Layout. Save your choice, then select and save it again to show the field. Layout stays visible until you choose to hide it; existing visibility settings are preserved. Hiding affects the Admin Panel only and keeps the saved layout, the Grid default, and API access unchanged.
Video Input Visibility
In the Console field visibility overview, open Videos to show or hide Aspect ratio and Chapters. Chapters controls the entire chapter list in General. Save your choices, then select and save them again to show the fields. Both inputs stay visible until you choose to hide them; existing visibility settings are preserved. Hiding affects the Admin Panel only and keeps stored values, chapter order, and API access unchanged. Saving still requires a title and a start time of 0 or more for every chapter row.
Moving Images Between Folders
In the Admin Panel image list, add the Folder column to move an image. The displayed folder changes after a successful request. If the request fails, an error notification appears and the previous folder stays displayed. Review the error before retrying; refresh the list if the connection was interrupted to check the saved folder.
Adding Attendees
In the Admin Panel, Add attendee requires a name and a whole quantity from 1 to 10. Email is optional; when supplied, it must be a valid email address. Correct the highlighted field before submitting. Inputs stay locked while the request is running, and a failed request retains your draft for a manual retry.
Event Cancellation And Trash
Before canceling an event, use the Console's event cancellation action to review its impact on future occurrences, registrations, holds, and paid orders. A refund requirement is a handoff to Commerce and Orders; it does not issue a refund.
An event with a future non-trashed scheduled occurrence cannot be moved directly to trash. The Admin Panel and direct API writes return 409 event_trash_requires_cancellation and ask you to cancel the event first. Once no future non-trashed scheduled occurrence remains, you can trash the event. Restoring it does not reopen canceled occurrences or reverse refund requirements.
If registration approval, cancellation, no-show marking, or occurrence cancellation fails, the confirmation stays open with the error and your note or reason. Review the message before retrying or canceling the dialog. A successful action closes it and refreshes the page.
Moderation And Support
When editing a community ban document, select Permanent first. The expiry input appears only for temporary bans and must contain a future time before saving. Permanent bans need no date. Saving a ban as permanent preserves its existing expiry. Switching back to temporary shows the date again; if it is past or empty, enter a future time before saving.
- Assign who reviews reports, comments, and customer-facing content.
- Decide how support receives form submissions or customer questions.
- Keep operational records reachable from Console, not in side spreadsheets.
Minimum Launch Checklist
- enabled content features have at least one real item
- each enabled area has an owner
- moderation or support queues are monitored
- publishing changes have a review habit
- empty enabled areas are either filled or disabled
Do not enable events for customers until event operations and calendar ownership are clear. Do not enable community until moderation ownership is clear.
Next Actions
- If sales is enabled, continue to Commerce Operations.
- If credentials or domains are needed, continue to Integrations & Keys.
- Before launch, run Launch Readiness.