> 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/quick-tips-for-using-the-quot-is-quot-filter.md).

# Quick Tips for using the "is" filter

* The “is” filter is **not** case sensitive.
* A space forms part of the string being searched for, unless it appears at the beginning or end of the criteria, in which case it will be ignored.
* **Exact matching**

  If no wildcard characters are included in the criteria, the filter will return records where the string is an exact character match.
* **Wildcards** ( **\***, **%** or **\_** )

  Asterisks ( **\*** ), percentage symbols ( **%** ) and under-scores ( **\_** ) can be used as wildcards.

  * **Multiple character wildcards**

    \* and % can represent multiple characters of any value, preceding or following one or more specific characters.

    *Example:*

    *Entering Sales\* in the filter would result in all records that begin with Sales appearing, like “Sales Auckland” and “Sales Wellington”.*
  * **Single character wildcards**

    \_ represents a single character of any value.

    *Example:*

    *If looking for records with 4 characters that must end in TG, you would enter \_ \_TG*
  * Multiple occurrences of **\*** and **%** are treated the same as a **\*** search.

    *Example:*

    *\*\*\*, %%% or \*\*% would all return the same results as \**
  * Spaces in between wildcards are treated as actual strings.

    *Example:*

    **\* \*** *(i.e.* **\*** *\<space>* **\*** *) would return any string that contains at least one instance of a space.*


---

# 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/quick-tips-for-using-the-quot-is-quot-filter.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.
