Warning!

It is HIGHLY RECOMMENDED to enable the feature this way, and to confirm the upgrade job completed with no errors. If Courses are not setup correctly, this could cause data issues down the line.

Important — this only prepares the data, not the UI:

Enabling Course Versioning runs a backend data update that creates Course Headers and populates the Version field on existing Course records. This process does not automatically expose the Version field (or any other versioning-related fields) anywhere in the user interface.

After enabling the feature, an admin still needs to perform their own analysis and decide where — if anywhere — versioning information should be surfaced, for example:

• Page Layouts — adding the Version field (and related fields, like Course Header) to the Course page layout(s)
• Lightning Record Pages — adding the field(s) to any Lightning App Builder pages/components
• Flows/Wizards — updating any Screen Flows or setup wizards that create or edit Courses, so users are prompted for or shown versioning data where appropriate

Until this configuration is done, the data will be correct behind the scenes, but users won't see or interact with it through the standard UI.

The same applies when disabling the feature. Disabling Course Versioning reverses the logic, but any data, fields, layouts, or flow steps you added to expose versioning will need to be reviewed and removed/reverted separately — disabling the feature does not automatically undo the data and UI changes you made.