# Fields and properties

## Fields

Fields allow content administrators to enter data into the backend of their GovCMS site. The fields available vary depending on the *content type*, however some fields are common (and **mandatory**) across all content types, including a *Title*.

Some fields are optional, for example the body field in a *Webform*.

Field settings, such as whether a field is optional or mandatory and the associated widget type are pre-configured by your site builder when building the site. For example, for an *Event* content type in GovCMS, the start and end date and time are logical and necessary, so they are configured to be mandatory fields.

<figure><img src="https://1079433754-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lyh9JMywljz0CN8oT8o%2Fuploads%2FiHhqM6SK2JSR18nrJTMs%2Fimage.png?alt=media&#x26;token=e4a1ce23-4298-4f87-a2b0-f3f379e403be" alt=""><figcaption><p>Event fields</p></figcaption></figure>

## Properties

A *property* is set at a deeper level (sometimes referred to as "baked in"). For example, all content has a date it was created on, and this date property plus any associated functionality is fixed. It is part of GovCMS and the underlying Drupal CMS.

The screenshot below shows both the *Author* property and the *Last saved* property which are visible to the author when editing the *Event*.

<figure><img src="https://1079433754-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lyh9JMywljz0CN8oT8o%2Fuploads%2FMLzjghpUj3UgpVFHjjYE%2Fimage.png?alt=media&#x26;token=a5523d1b-ec5b-4d9d-9c85-53a41287330a" alt=""><figcaption><p>Event property fields</p></figcaption></figure>
