> 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/creating-visitor-type-and-host-type-groups.md).

# Creating Visitor Type and Host Type Groups

### Definitions

**Visitor Types** are used to determine the:

* details to be captured for a visitor of that type
* Host Types valid for a visitor of that type
* access which may be assigned to a visitor of that type
* layout of the badge to be printed for a visitor of that type

**Host Types** determine which cardholders may meet with or escort a visitor of a particular visitor type. A Host Type may be assigned to one or more Visitor Types, and more than one Host Type can be assigned to a Visitor Type.

### Introduction

Visitor Types and Host Types are implemented in Command Centre using Access Groups. This procedure describes how to create an Access Group to be used as a Visitor Type Group or Host Type Group.

**IMPORTANT:**

Access Groups are typically used to control access to Access Zones. Access Groups created for Visitor Types cannot be used to control access to Access Zones. No real access should be assigned to Visitor Type Groups as they will be assigned to the visitors when they are added to the visit. They will not be removed from these groups when the visit is finished.

To avoid having to maintain Host Type Groups when new permanent cardholders get added to the system, existing Access Groups can be used as Host Type Groups. However, within Visitor Management, any one group cannot be a Visitor Type group, a Host Type group and the Visitor Access group, (i.e. the actual group that provides access for visitors). Therefore, if you do elect to use existing Access Groups as your Host Type Groups, you will need to create separate groups to provide visitors with access on site.

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

### Procedure

To configure Access Groups which provide access to zones, use the [Setting up Access Groups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/setting-up-access-groups.md) procedure. To configure Visitor Type and Host Type Groups, use the following procedure:

**Note:** Configuring Membership Defaults (on the **Cardholder Membership** tab) for a Visitor Type or Visitor Access access group is not recommended as Visitor Management adds and removes cardholders from Visitor Type and Visitor Access access groups on a daily basis.

1. Click **Manage** from the menu bar.
2. Click **Access Groups**.

   The **Access Group** List Window opens.
3. **Right click** and select **New\...Access Group**.

   By default the General tab displays.
4. Enter an appropriate **Name** for the group.

   **Note:** Each Visitor Type Group should be given a meaningful name as this will appear in both the Command Centre configuration and in the Visitor Management application.

   If you have used existing Access Groups as your Host Type Groups, there is no need to alter these names.
5. Click the **OK** button to save the group.
6. Repeat Steps 3 to 5 for every Visitor Type and Host Type required.

### Important

For Visitor Type Groups:

* Do **not** assign any cardholders. Instead, this is done when visitors are added to "Visits" in the Visitor Management application.
* When you get to the **Personal Data** tab, any Personal Data Fields (PDFs) that you assign to the Access Group must not have the "Required Field" checkbox checked on the **Type** tab of the PDF properties.


---

# 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/creating-visitor-type-and-host-type-groups.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.
