> 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/operate/visitor-management-client/faqs-visitor-management.md). # FAQs - Visitor Management

Question	Answer
Can two users edit the same visit?	No. A visit can only be edited by one user at a time.
Why am I unable to cancel a visit?	If a card has been assigned to a visitor on a visit, the visitor needs to be marked off-site or their access card unassigned before the visit can be cancelled.
Why am I unable to assign a card?	Either: This card has already be assigned to a visitor. View the status bar to confirm who this card has been assigned to.OR: This person may already have a card assigned, (e.g. this person is already on a visit or this person is a permanent cardholder).
Can I control what access the visitor is granted?	Yes, if your reception and user privileges have been configured in Command Centre to grant access, you can control what access is assigned to a visit, for a visitor.
Can I grant a visitor additional access while on a visit?	Yes, if you have the required user privileges, you can assign additional access to the visit that the visitor is on, either before the visit starts or while the visit is in progress.
Can I pre-register visitors and groups of visitors?	Yes, create a visit, add visitors and set the visit date for the future.
Can I customise the badge label?	Yes, a badge label can be customised in Command Centre to incorporate a background template,(e.g. colour), visit details, visitor details, visitor photograph, company name, company logo or badge text.
When does the access card assigned to a visitor expire?	Access is granted when the visitor is marked on-site. Access is removed when the visitor is marked off-site or temp off-site. Access can also be removed from the visitors visit, at any stage of their visit.
Can I use a biometric reader?	Yes, a biometric reader, (e.g. fingerprint reader) can be used to identify hosts (permanent cardholders in Command Centre).
Can I use passwords to protect the data?	Yes, a username and password is required to logon. User privileges determine what you can see and what actions you can perform.
What reports can I produce?	You can generate a report that records the information on the Home and Find Visit screens. What information is shown on these screens is up to you, (e.g. display the time and attendance for a particular visitor).

--- # 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/operate/visitor-management-client/faqs-visitor-management.md?ask=&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.