> 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-2-single-company-config-per-reception.md).

# Example 2: Single Company installation, different Visitor Management configuration for Receptions

### Introduction

The following example shows the recommended set up where the system is for a single company, but there is a requirement to configure the Receptions differently for Visitor Management.

### Scenario 1

This table shows the privileges required assuming that the Receptionist has the ability to:

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

Additionally the table 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-4accfb49c3b240611f7659d7dde9188a39435436%2Fconfig_eg2_scenario1_html.png?alt=media)

**Note:** In this setup the "Manage Receptions" privilege is required in the following divisions:

1. each Division containing a Reception, (e.g. Division 1 and/or Division 2) for which the user can act as a Receptionist. This determines the Receptions available for the Receptionist on their Home screen.
2. the Visitor Division. This indicates that the user is a Receptionist rather than someone who can only pre-register visits, and will allow them to see the Visitor Card Type details, required for validating that the card they have assigned to a visitor is valid, and is needed to perform the necessary configuration validation at logon.

### 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.

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

**Note:** In this setup the "Manage Receptions" privilege is required in the following divisions:

1. each Division containing a Reception, (e.g. Division 1 and/or Division 2) for which the user can act as a Receptionist. This determines the Receptions available for the Receptionist on their Home screen.
2. the Visitor Division. This indicates that the user is a Receptionist rather than someone who can only pre-register visits, and is needed to perform the necessary configuration validation at logon.

### 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-719b0a4ee9316048549814cb940fd962f8c0d46e%2Fconfig_eg2_scenario3_html.png?alt=media)

The "View Visits" privilege is required in Divisions 1 and 2 so that users can see Receptions in those divisions.

### Recommended Operator Groups for Example 2

For the setup described in Example 2, (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>"Manage Visitor Attributes" in the <em>Find Visitor in this Division</em></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>"Manage Receptions" in the <em>Save Visitor in this Division</em></td></tr><tr><td>Group 6</td><td>"View Events and Alarms" – for card badging, and "Run Macros" – for running macros in the <em>Save Visitor in this Division</em></td></tr><tr><td>Group(s) 7</td><td><p>"Manage Receptions" in Division 1</p><p><strong>Note:</strong> There should be one group for each division which has a Reception. Alternatively a single group could be used to assign the "Manage Receptions" privilege for all the Visitor Management configuration divisions.</p></td></tr><tr><td>Group(s) 8</td><td><p>"View Visits" in Division 1<br>This provides someone who can only pre-register visits with the privileges to see the Receptions in that Division without the ability to Manage those Receptions.</p><p><strong>Note:</strong> There should be one group for each division which has a Reception. Alternatively a single group could be used to assign the "View Visits" privilege for all the Visitor Management configuration divisions.</p></td></tr></tbody></table>

For a Reception where a Receptionist can create and edit visits, Groups 1, 2 (optional), 4, 5, 6 (optional) and 7 (whichever group contains the Reception) are required.

For a Reception where a Receptionist can only view visits, Groups 1, 3, 5 and 7 (whichever group contains the Reception) are required.

For a Reception where the user only has the ability to pre-register visits, Groups 1, 4 and 8 (whichever group contains the Reception) 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-2-single-company-config-per-reception.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.
