Settings

CONTENT_ENABLED

A project setting that records the tenant CMS state shown in the Ovok Console. CMS access is managed separately.

A Boolean project setting that records the tenant-level state of the CMS in the Ovok Console. Ovok's public-delivery routes do not read this setting directly. The Console also manages authoring access and billing, so changing only this key through the settings API does not enable or disable the complete CMS workflow.

TypeBoolean setting
Change withPUT /v1/project/settings/CONTENT_ENABLED
Who can change itProject admin; the CMS itself is enabled for the tenant in the Console
When unsetReads as false; the value has no effect either way
Set on new projectsNot set by any project-creation route
Set byThe Console, when you enable the CMS
Effect todayNone. The CMS routes do not check it.

Why it is listed

CONTENT_ENABLED is one of the keys that GET /v1/project/settings returns and PUT /v1/project/settings/:key accepts, so it appears in the settings record of every project.

curl --request PUT \
  --url 'https://api.sandbox.ovok.com/v1/project/settings/CONTENT_ENABLED' \
  --header "Authorization: Bearer ${OVOK_TOKEN}" \
  --header 'Content-Type: application/json' \
  --data '{"enabled":true}'

The response is the full settings record, so you can confirm the value was stored. Storing it changes no behaviour.

Gotchas

  • Do not use it as a feature gate. Public-delivery routes do not check the setting itself. CMS access also depends on Console-managed authoring access.
  • Read it as a marker, not the whole CMS state. true records the tenant's CMS state in this project's settings. The Console workflow also manages authoring access and billing; use the Console to enable or disable the CMS.
  • It is not a project feature. Features are the names you manage with PATCH /v1/projects/me/features; this key lives with the settings, and enabling it does not add anything to the feature list.
  • Writes still follow the normal rules. Admin only, and a concurrent change answers 409; read the settings again and retry.

Last updated on

On this page