> 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-workspaces/opening-the-administration-workspace/searching-columns.md).

# Searching columns

The **Settings** option (in the Navigation Panel on the left) allows you to choose which columns appear in the search results. Go to **Settings**, then **Cardholders**, then **Search Page**.

Each of the six drop-downs sets one column, and the columns you choose also decide which fields you can search by. You can choose from First Name, Last Name, Card Number(s), Description, Last Zone Entered, Authorised, Division and PDFs. Up to six columns can be shown on a desktop.

Column settings apply to all operators. Changing them requires the "Edit Site" or "Advanced User" privilege on the root division.

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

**Showing the History tab**

Under **Settings** > **Cardholders** > **Layout**, the **Show History Tab** switch controls whether the **History** tab is shown to operators who do not have the "View Events" privilege. Turn it off to hide the tab from those operators. The switch is on by default.


---

# 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-workspaces/opening-the-administration-workspace/searching-columns.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.
