> 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/products/cc-software/configure/configuration-scenarios/scenario-easiest-way-to-allocate-crede.md).

# Allocate credentials

Issue Gallagher Mobile Credentials by email to eligible cardholders and readers.

If a facility uses Gallagher readers and the version installed on site supports them, **Gallagher Mobile Credentials** are the least interactive method of granting a person access to that facility.

* Mobile credentials can be issued via email, without the cardholder needing to visit an office to obtain a physical card.
* Credentials are issued from Command Centre through the Command Centre Cloud service directly to the cardholder's mobile device.
* They work on **HBUS-connected readers** connected to **7000 series controllers**.
* Every site is entitled to **10 free mobile credentials by default**. More can be purchased if required.

### Related links

* [Mobile Connect](/knowledge-hub/products/cc-hardware/credentials/mobile-connect.md). Licensing, prerequisites, configuration, and troubleshooting for mobile credentials.


---

# 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/products/cc-software/configure/configuration-scenarios/scenario-easiest-way-to-allocate-crede.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.