> 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/configuration-client/licensable-features/cardholder-competencies/reporting-on-cardholder-competencies.md).

# Reporting on Cardholder Competencies

### Introduction

This procedure describes how to run a Cardholder Report that includes Cardholder Competency details. Operators must have the "View Cardholders" and the "Edit Report Descriptions" privileges to create, save, edit and delete Cardholder Reports.

**Notes:**

* Cardholder reports can be scheduled to run automatically at regular times (via a Macro). For further information refer to [Automatically Generated Reports](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/automatically-generated-reports.md) and [Creating a new Macro](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/macros/creating-a-new-macro.md).
* **Detailed** Cardholder Reports can also be run from:
  * the Cardholder List Window.

    See [Running a Cardholder Report from a Cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/running-a-cardholder-report-from-a-cardholder.md) for further detail.
  * the **Competencies** tab on the Cardholder properties. The competency options are selected by default using this method.

    See [Assigning Competencies to cardholders](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/cardholder-competencies/assigning-competencies-to-cardholders.md) for further detail.

### Procedure

1. Click **Report** from the menu bar, then **Report Descriptions**.

   The **Report Description** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** and select **New\...Cardholder Report**.

   The "Report Style" screen of the Cardholder Report wizard displays, allowing you to select either a **Detailed** or **Summary** version of the report.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-7d3f592f8c5964ac870bf51f17442a94b611bcdb%2Fchold1_competencies.png?alt=media)
3. What style of the report do you want to run?

   <table><thead><tr><th width="98">If...</th><th>then...</th></tr></thead><tbody><tr><td>Detailed</td><td><p>check the <strong>Include Competency Details</strong> checkbox, (and any of the other checkboxes you require for the report), and click the <strong>Next</strong> button.</p><p>Go to Step 4.</p></td></tr><tr><td>Summary</td><td><p>click the <strong>Summary Report</strong> radio button, then the <strong>Next</strong> button.</p><p>Go to Step 6.</p></td></tr></tbody></table>
4. The "Competency Options" screen of the wizard displays, which allows you to specify the specific Competency information you wish to include in the report.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5746cebc257e8290d916f4ae08eff9547a35aea4%2Fchold2a_competencies.png?alt=media)

   There are four options available, and by default they are all selected. Each option generates a separate section in the report as follows:

   **Competencies assigned to Cardholders**

   This option lists all competencies assigned to a Cardholder where the operator has view or edit access to the competency. This creates a table with the following columns:

   * Competency Name
   * Expiry Date
   * Notice Period (in days)
   * Expired (displays Yes = expired competencies; blank = non-expired competencies)
   * Disabled
   * Will Re-enable
   * Comment

   **Competencies required to enter Access Zones**

   This option lists competencies required to access each Access Zone that a Cardholder can otherwise access based on their Access Group memberships. This creates a table with the following columns:

   * Access Zone
   * Competency Name

   Active Access Group memberships are determined based on the time the report is generated. Competencies are excluded where the operator does not have view or edit access. Each Access Zone with one or more Competencies that the operator cannot view includes the entry '{Privilege Restricted Competencies}'.

   **Access Zones that cannot be accessed due to...**

   This option lists Access Zones that can be accessed at the time the report is generated, based on Access Group memberships, but cannot be accessed based on held Competencies. This creates a table with the following columns:

   * Access Zone
   * Competency Name (only those that are preventing access)
   * Reason, (i.e. Missing, Expired or Disabled)

   Competencies are excluded where the operator does not have view or edit access. Each Access Zone with one or more Competencies that the operator cannot view includes the entry '{Privilege Restricted Competencies}'. This table can be sorted by Access Zone and then Competency Name, or vice versa.

   **Competency exempt Access Groups**

   This option lists all Competency Exempt Access Groups to which a Cardholder belongs, and the Access Zones to which they provide access. This creates a table with the following columns:

   * Access Group
   * Access Zone (one or more per Access Group)
   * Schedule Access

   The Schedule Access column displays 'No Access' when the Cardholder's Access Group memberships do not provide access to the Access Zone at the time the report is generated.
5. Check the option(s) you require, and click the **Next** button.

   Go to Step 13.
6. The "Report Content" screen of the wizard displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-498e33d03621d0b1c0d2903f194c91e5af5bcb45%2Fchold4.png?alt=media)

   The **Summary Report** always includes the Cardholder's first and last names, but this screen allows you to select up to eight additional Cardholder fields (by marking them with a tick), from the list provided.
7. Scroll down the list to the Competency fields.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2d39e50ed1e5a5f082f1659abd8f986526769844%2Fchold4_competencies.png?alt=media)
8. Select the Competency fields you want to include in the report, and click the **Next** button.

   The "Report Layout" screen of the wizard displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-241c17567ba4404a07dbafb6c460a140a6506c67%2Fchold7_competencies.png?alt=media)

   This page allows the operator to configure the layout of the report.

   You can determine the position of the columns horizontally across the page, as follows:

   1. Move the mouse pointer to the column header you want to reposition.

      The mouse pointer changes to a hand symbol.
   2. Click and hold down the mouse button.

      The hand changes indicating it is grabbing the header.
   3. Move the hand (and hence the column header) to the desired new position.
   4. Release the mouse button.

   You can also resize the width of the columns, as follows:

   1. Move the mouse pointer to a column separator.
   2. When the mouse pointer changes to a double-ended arrow ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-7a956876208764eb7a1fe7dda7f305e2ab531fb8%2Farrow_cross.png?alt=media), drag the column separator in the required direction to achieve the desired column width.
9. Click the **Next** button.

   The "Competency Filter"screen of the wizard displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-3fa2fe85e9bdf64743fb685727214b9a20e38cd9%2Fchold9_competencies.png?alt=media)

   This screen provides a list of Competencies that an operator may include in the report. Competencies shown here are restricted to those under the Division of the operator.
10. Select either **All Competencies**, or drag and drop those that you want included in the report from the left to the right hand grid.
11. Click the **Next** button.

    The "Competency Date Filter" screen of the wizard displays.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2b9766d4ab18b2f55ab42377515aad00a94da7af%2Fchold9a_competencies.png?alt=media)

    This screen allows you to restrict the report to Competencies that have an expiry date or a first expiry-due warning date within an operator specified date range.

    **Note:** By default, the "No Filter" option is selected. By leaving this selected, no restriction will be applied.
12. Make the selections you require, and click the **Next** button.
13. The "Select Cardholders and Operators" screen of the wizard displays.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-21d7a4d9b8a8a2c6c2b8583bd7cfe1a0b7d5ad60%2Fchold3.png?alt=media)

    This screen provides a list of Cardholders that may be included in the report. Cardholders shown here are restricted to those under the Division of the operator.
14. Select either **All Cardholders and Operators**, or drag and drop those that you want included in the report from the left to the right hand grid.

    **Note:** Alternatively, you can open the Access Group List Window and drag and drop those Access Groups you require onto this screen.
15. Click the **Next** button.

    The "Regional Settings" screen of the wizard displays.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2390fadd6a1b5cde8f3e4fe96034cb3d29e1dc32%2Fchold8.png?alt=media)

    This page allows a time zone and/or language to be selected for the report. These options are specifically provided to support the Cardholder Report, (i.e. when the report is run via a macro on the server). Selection of a time zone is optional, as it is only required for Command Centre sites that span time zones. Selection of a language is also optional as it is only required for sites that have multiple languages.

    If no time zone is selected, the report uses the time zone of the Command Centre server, only if the report was initiated from a macro which was triggered by an Action Plan, or a macro that was run from its schedule. In all other cases, the report uses the time zone on the workstation of the operator who has run the report, or the time zone on the workstation of the operator who ran the macro that triggered the report.

    If a time zone is selected, when the report is run, all dates and times within the report will display in the selected time zone. Any dates and times configured within the report are assumed to be within the selected time zone (rather than the time zone on the configuring operator's workstation).
16. Click the **Next** button.

    The "Report Generation and Saving" screen of the wizard displays, which is the same for all report types, and provides the same options. Refer to [Report Generation and Saving](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/creating-a-new-report.md) in the *Creating a new report* procedure for further detail.


---

# 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/configuration-client/licensable-features/cardholder-competencies/reporting-on-cardholder-competencies.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.
