Skip to content

Entries

Entries are the individual content items created from your content models. For example, if you have a Blog Post model, each blog post you create is an entry.

Before you can work with entries, open the content model they belong to.

  1. Go to Content.
  2. Select a content model from the sidebar.
  3. Browse the list of entries, or use search to find a specific one.

To create a new entry:

  1. Click Create Entry.
  2. Fill in the fields defined by the content model.
  3. Click Save.

After saving, the entry usually remains in draft until you change its visibility settings and save again.

To update an existing entry, open it from the list, make your changes, and save again.

Field changes and visibility changes are saved together, so the sidebar always shows the result you are about to save.

When you open an existing saved entry, the editor sidebar includes separate Tasks and Notes cards. Use Notes for internal discussion on the entry, and use Tasks for entry-linked work, including review change requests when your workflow uses them. Broader follow-up also appears in Tasks, Mentions, and the dashboard cards in the Studio.

For step-by-step guidance, see Notes and Tasks.

When the content model has a preview URL template configured, the entry editor toolbar includes Open Preview and a copy control (left of Save Changes). Links use the last saved entry values. Configure templates under Models or see Preview Links.

For content entries, visibility is managed from the Visibility section in the editor sidebar.

The visibility badge shows the current state of the entry:

  • Draft: the entry is not available through the API
  • Live: the entry is published and available through the API
  • Scheduled: the entry will go live automatically at the selected time
  • Expired: the entry was previously live and was automatically unpublished at its scheduled end time

When a workflow is enabled for a content type, the editor includes Workflow controls. The entry moves between workflow stages (for example draft, in review, done) that reflect your team’s editorial process. Those stages are separate from visibility (draft / live / scheduled / expired), which controls when content is available through the API. Depending on your permissions and configuration, you may need to advance the entry through the workflow stages before you can publish or schedule go-live.

For detailed instructions on publishing, scheduling, and returning to draft, see Scheduling & expiration.

If your project supports multiple locales, entries can contain different values for localized fields in each language or region.

To work with localizations:

  1. Go to Content and open the relevant content model.
  2. Choose a locale from the sidebar, or use the localization link next to an entry.
  3. Open an existing localized entry, or create a new localization.
  4. Update the localized fields and save your changes.

Localized fields can have different values in each locale. Non-localized fields remain the same across all locales.

Use Translate Content when you want AI help translating entries into other project locales. You can start a translation run from the Translate Content page, or select entries from a content model list and choose Translate.

If your team wants translations to happen automatically when entries are created, updated, or published, use Autotranslation Rules.