> 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-4-multi-tenant-common-lobby.md).

# Example 4: Multi-tenanted installation, common lobby Reception, no data separation for the Companies

### Introduction

The following example shows the recommended set up where the system is for a multi Company installation and visitors are shared across companies.

### Scenario

This table shows the configuration recommended for this scenario:

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

### Recommended Operator Groups

The Operator Groups will be based on those shown in [Recommended Operator Groups for Example 1](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#recommended-operator-groups-for-example-1).


---

# 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-4-multi-tenant-common-lobby.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.
