> For the complete documentation index, see [llms.txt](https://salsa-digital.gitbook.io/govcms-content-administration/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://salsa-digital.gitbook.io/govcms-content-administration/unit-2-more-about-govcms/fields-and-properties.md).

# 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="/files/vBSGNkgRcnHi80oBqzFN" 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="/files/jCe2JnlYptrNS6TuvDD7" alt=""><figcaption><p>Event property fields</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://salsa-digital.gitbook.io/govcms-content-administration/unit-2-more-about-govcms/fields-and-properties.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.