> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/personal-data-fields/creating-a-new-personal-data-field.md).

# Creating a new Personal Data Field

Perform the following procedure to create a new Personal Data Field:

1. Click the **New Personal Data Field** button on the Viewer Navigation Panel.

   The new Personal Data Field is added to the Viewer Navigation Panel, and the Personal Data Field Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-21b34469d9ec3b0c2fa0b8022be6e18ae139f245%2Fpdfconfig_popup.png?alt=media)
2. If you want to replace the default name the system has given the Personal Data Field, enter a new name in the **Name** field (limited to 60 characters).
3. If required, enter a logical **Description** (limited to 200 characters).
4. The **Division** button defaults to the name of the last Division in which the Operator created a Command Centre item, regardless of whether it was created in Configuration Client or via Command Centre Client.

   If this is not the appropriate Division for this Personal Data Field to be in, select a Division as follows:

   1. Click the **Division** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-5ea28b89c753564de542b1b9c1b328d1e0fc8c60%2Fselectdivisionforviewer_popup.png?alt=media)
   2. Select the appropriate Division.
   3. Click the **OK** button.

      The pop-up closes and the button changes to the name of the Division you selected.

   **Note:** If you have not set up Divisions yet, you can add these to your Personal Data Field at a later stage.
5. Click the **Close** button.

   The Personal Data Field Configuration pop-up closes.

   There are two tabs, (i.e. **Personal Data Fields** and **History/Notes** ). The **Personal Data Fields** tab displays by default. It determines the type of data to be entered against the PDF and which Access Group(s) the Personal Data Field is to be attached to

   By default "Text" populates the **Data Type** field.
6. Click within the **Data Type** field and select the appropriate type from the drop-down list.

   **Note:** With the exception of the **Numeric** type, each type has additional information that must be entered, some of which is common to all types, while other information is specific to individual types, as follows:

   <table><thead><tr><th width="168">If you select...</th><th>the...</th></tr></thead><tbody><tr><td>Text, or any contact PDF types, (i.e. Address, Phone, Email or Mobile)</td><td>following additional fields display:<br><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-55ebfab05c26e438eb78bc7e515b7384990cf824%2Fpdftext.png?alt=media" alt=""><br>The <strong>Regular Expression</strong> feature is for text and contact type PDF data validation to allow the enforcement of text values. It allows you to write a regular expression that will force PDF entered values to obey the rules of the expression. If values are entered that break the expression, then an error message displays detailing the expression requirements.<br>See <a href="https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/personal-data-fields/regular-expression-settings.md">Regular Expression Settings</a> for further detail on entering information into this section.</td></tr><tr><td>Text - List</td><td>following additional fields display:<br><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7e98f4407f38103d8bd1625950b72619c87a5b85%2Fpdftextlist.png?alt=media" alt=""><br>These fields allow you to define a set of entries that may be selected from, when entering data against a cardholder. To do this, enter a value in the List Values field, then click the <strong>Add</strong> button.<br>When the <strong>Restrict to List</strong> option is enabled the <strong>Default Value</strong> must be one of the list values or blank. If <strong>Restrict to List</strong> is not enabled, free text entries can be entered against a cardholder.</td></tr><tr><td>Image</td><td>following additional fields display:<br><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-c394e84b1a5a00abab8d3058aca014f36a1e8369%2Fpdfimage.png?alt=media" alt=""><br>These fields allow you to specify details about the image that is saved to the database.<br>The <strong>Image Type</strong> can be JPEG, Bitmap or PNG.<br>Check the <strong>Profile Image</strong> checkbox if you want this Image PDF (containing the cardholder photo) to be shown on the Mobile Client Details screen.<br><br><strong>Note:</strong> Only one Image PDF will be used for each cardholder. If a cardholder has more than one Image PDF captured and they all have the <strong>Profile Image</strong> checkbox enabled, the image with the lowest sort order will display.<br>Refer to <a href="https://help.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/working-with-viewers/tile-actions/cardholder-images-tile-actions.md">Capturing an Image</a> for the procedure on how to capture images for an Image Personal Data Field.</td></tr><tr><td>Date</td><td><strong>Default Value</strong> field changes to a Date control, and two additional fields display:<br><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-9170db00cc3281a4faa09a5bfbc07afb2b046629%2Fpdfdate.png?alt=media" alt=""><br>Leave the <strong>Default Value</strong> field blank if you do not want a default.<br>A lower and/or upper date range may be specified to control the dates entered into the PDF.<br><strong>Note</strong>: The dates will display on-screen and in reports in the date format specified in the workstation settings.</td></tr></tbody></table>
7. Check the following boxes as necessary:

   <table><thead><tr><th width="168">If...</th><th>is checked, then...</th></tr></thead><tbody><tr><td>Required Field</td><td>Data for the Personal Data Field will be mandatory when editing a cardholder.</td></tr><tr><td>Unique Value</td><td>an operator will be prevented from entering the same value across multiple cardholders (although the system will allow a "no data" value to be entered multiple times).<br>The <strong>Default Value</strong> field is disabled.</td></tr></tbody></table>

   **Note:** The **Unique Value** field is not available for Text - List, Image and Date types.
8. Click within the **Default Privilege** field and select the appropriate privilege (i.e. type of access), from the drop-down list.

   This determines the base operator rights for this Personal Data Field.

   <table><thead><tr><th width="168">If you select...</th><th>then...</th></tr></thead><tbody><tr><td>Editable (default)</td><td>operators with the "View Cardholders" privilege in a division can view the Personal Data Field value but not create or edit it.<br>Operators with the "Edit Cardholder Personal Data" privilege in a division can create or edit the Personal Data Field values of a cardholder in that division.</td></tr><tr><td>Hidden</td><td>operators will not see the cardholder information recorded for this Personal Data Field for cardholders in this group's Divisions, or even see that it exists.</td></tr><tr><td>Revealable</td><td>operators with the "View Cardholders" privilege in a division can view the Personal Data Field value (under the <strong>Personal Data</strong> tile of the Cardholder Viewer), click on the value that says hidden.<br>Operators with the "Edit Cardholder Personal Data" privilege can view the Personal Data Field by clicking on the value that says hidden.</td></tr><tr><td>View Only</td><td>operators with the "View Cardholders" privilege in a division can view the Personal Data Field value.<br>Operators with the "Edit Cardholder Personal Data" privilege can view the Personal Data Field value, but not create or edit it.</td></tr><tr><td>Revealable and Editable</td><td><p>operators with the "View Cardholders" privilege in a division can view the Personal Data Field value (under the <strong>Personal Data</strong> tile of the Cardholder Viewer), click on the value that says hidden, but not create or edit it.<br>Operators with the "Edit Cardholder Personal Data" privilege can view by clicking on the value that says hidden can view or edit the Personal Data Field value of a cardholder in that division.<br><br><strong>Notes:</strong></p><ul><li>Revealable and Editable PDFs are not available in REST or Mobile Client.</li><li>Revealable or revealable/editable PDFs that are included will not log the new access event when a report is run, a search via REST is made, or there has been an operator event.</li></ul></td></tr></tbody></table>

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-635e52f128526e4bf27f664051e2f6fd299b8ae0%2Fpersonaldatatile.png?alt=media)

   Every time a PDF hidden values are clicked (when the privilege is set to "Revealable" or "Revealable and Editable"), there is an Operator Event in the form of *Operator "View Site, VS" revealed the value of the "Address R\&E" field for "Configure Site, CS"*, from the "Source" of the Workstation that the operator was logged into.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-1e388e8515c8976d842359a2ea46310b83b542d9%2Frevealablepdfevent.png?alt=media)

   **Notes:**

   * The **Default Notifications** checkbox will be revealed when the **hidden value** for the PDF is clicked, (i.e. ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-38596f84b6b327bde06a1a00950d5c9ba22f401c%2Fpdf_hiddenvalue.png?alt=media) ).
   * The system operator does not have the reveal option visible, as they can see everything anyway.
   * A field which is not editable will have its title rendered in grey.
9. Alter the **Sort Order** field if necessary. This controls the order in which PDF records are shown in the cardholder property page.

   **Note:**

   The lower the number, the higher up the list it will display, (e.g. 1 will display the PDF at the top of the screen, 100 will put it at the bottom, and if all are set to the same number they will display in alphabetical order).
10. Select the Access Group(s) appropriate for this Personal Data Field, as follows:

    1. Click the **Add Access Group** button.

       The Add Access Groups pop-up displays.

       ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-a5b99cb369dc346f3178b3178d1742a5ac3c4d57%2Faddaccessgrps_popup.png?alt=media)
    2. Click the checkbox next to each group you want to include, and click the **Add Selection** button.

       The pop-up closes and each of the selected group(s) appear in the **Access Group** grid.

    **Note:** If you decide to remove a group from the list, the **Remove** button allows you to do so.
11. If you want to record any note(s) about the Personal Data Field, click the **History/Notes** tab.

    Refer to [History/Notes tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/history-notes-tab.md) for further detail.
12. Click the **Save** button.

    A new Personal Data Field has been created.

    **Note:**

    Once a Personal Data Field has been created and data has been recorded against it, the ability to alter its Data Type will not be available.

    For recording cardholders personal data against PDFs, see Editing a Cardholders PDF data for the procedure.

### Hints

{% hint style="info" %}
**Editing and Deleting Personal Data Fields**

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/deleting-items.md) for procedures on how to edit and delete Personal Data Fields.

**Note:** Deletion of a Personal Data Field is only allowed if it is not currently assigned to be used anywhere in the system, except if it is saved against a report.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/personal-data-fields/creating-a-new-personal-data-field.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
