Purpose: This article explains how to configure the structured fields and descriptive content used on course templates. These fields control what data can be captured on templates, how your catalog is presented in portals, and what values are exposed via API and reporting.
Related: Managing courses in Administrate | Create a course | Courses, Course Templates, and Events: Structure and Inheritance
Mental model: field definitions vs template values
- Field definitions determine which inputs exist on course templates (for example: code, duration, marketing fields, internal reporting fields).
- Template values are the data you enter into those inputs on a specific course template.
Think of field definitions as the “schema” for course templates. Changing definitions affects how new templates are structured and what fields administrators see when editing templates.
Where course fields are defined
Course fields are defined centrally in Control Panel → Courses. Each defined field becomes an editable input when creating or editing a course template.
Edit course field definitions
- Go to Control Panel.
- Open Courses.
- Open the area where course fields are managed (course configuration / fields list).
- Create, edit, or reorder fields as needed for your workflow.
- Select Save to apply changes.
If your Control Panel uses a separate area for “field definitions” vs “course templates,” apply the same logic: you are editing the definitions that drive the template UI.
Add or update course descriptions
Descriptions and rich text fields are commonly used for learner-facing catalogs, portals, and marketing pages. Keep them readable, structured, and consistent.
- Open the course template you want to update.
- Locate the description field (or the relevant rich text field).
- Enter or update the content.
- Select Save.
Why this matters
- Ensures consistent catalog presentation across templates and deliveries.
- Improves reporting and downstream integrations by keeping data structured.
- Reduces duplication and rework during event creation.
- Helps prevent “free-form” content from contaminating structured fields.
Editing guidance and guardrails
- Use consistent naming conventions and formatting for fields (especially codes and internal identifiers).
- Avoid putting long, unstructured text into header-style fields intended for reporting.
- When pasting content from tools like Microsoft Word, review formatting to prevent unwanted HTML.
- Treat changes to field definitions as structural: coordinate with anyone who relies on APIs, exports, or integrations.
Change impact: Changes to course field definitions affect how templates are structured going forward. They do not automatically rewrite existing course templates or historical event data unless you explicitly update those records.