> 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/visitor-management/command-centre-site-configuration/configuration-examples/example-1-single-company-single-config.md).

# Example 1: Single Company installation, single Visitor Management configuration

### Introduction

The following scenarios show the recommended set up where the system is for a single company with multiple Receptions. The Visitor Management configuration requirement is the same for all Receptions.

### Scenario 1

The table below shows the privileges required for the Receptions where the Receptionist has the ability to:

* create and edit visits,
* create and edit visitor cardholder records,
* manage the Reception(s), (i.e. view the Home screen, perform the Visitor Management actions and print reports).

Additionally, it shows the privileges required if the Reception is set up for the badging of cards and the running of Macros (which is optional).

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

To assign an access card to a cardholder the operator needs the "Create and Edit Cardholders" privilege in the division that the cardholder is stored. To prevent a permanent cardholder's existing access from fraudulently being given to a visitor the Visitor Management application will not allow a second card to be assigned to someone who already has a card assigned in the system. Therefore, the only circumstance where the system would allow the assignment of a Visitor Card to a permanent cardholder, and therefore require "Create and Edit Cardholders" privilege in the permanent cardholder division, would be where they did not already have a card assigned.

### Scenario 2

The table below shows the privileges required for the Receptions where the Receptionist only has the ability to:

* view visits and visitor cardholder records,
* view the Home screen, and
* print reports.

To perform any actions the Receptionist would need "Edit Visits" privileges, so it is not possible to configure the system to allow the user to perform the Visitor Management actions but not directly edit the visit.

**Note:** In this sceanrio, the ability to View Visitors is inherited from the "View Cardholders" privilege in the parent division.

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

### Scenario 3

The table below shows the recommended set up for users who can only pre-register visits.

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

### Recommended Operator Groups for Example 1

For the setup described in Example 1, (i.e. scenarios 1, 2 and 3), it is recommended that the following Operator Groups are created in order to simplify the allocation of user privileges:

<table><thead><tr><th width="162">Operator Group Name</th><th>Privileges / Divisions</th></tr></thead><tbody><tr><td>Group 1</td><td>"View Cardholders" and "View Cardholder Notes" in the <em>Find Visitor in this Division</em></td></tr><tr><td>Group 2</td><td><p>"Manage Visitor Attributes" in the <em>Find Visitor in this Division</em></p><p><strong>Note:</strong> Where a Receptionist will be assigning escorts to visitors in a Division for which they only have "View Cardholder" privileges, (likely where the visitor is a permanent cardholder), the "Manage Visitor Attributes" privilege should be granted in that Division to enable them to perform that action.</p></td></tr><tr><td>Group 3</td><td>"View Visits" in the <em>Save Visitor in this Division</em></td></tr><tr><td>Group 4</td><td>"Edit Visits", "Create and Edit Cardholders", "Edit Cardholder Notes" and "Modify Access Control" in the <em>Save Visitor in this Division</em></td></tr><tr><td>Group 5</td><td><p>"Manage Receptions" in the <em>Save Visitor in this Division</em><br>Optionally: (in the <em>Save Visitor in this Division</em>)</p><ul><li>"View Events and Alarms" – for card badging</li><li>"Run Macros" – for running macros</li></ul></td></tr></tbody></table>

For a Reception where a Receptionist can create and edit visits, Groups 1, 2 (optional), 4 and 5 are required.

For a Reception where a Receptionist can only view visits, Groups 1, 3 and 5 are required.

For a Reception where the user only has the ability to pre-register visits, Groups 1 and 4 are required.


---

# 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/visitor-management/command-centre-site-configuration/configuration-examples/example-1-single-company-single-config.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.
