> 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/command-centre-client/configuring-command-centre/administration/bulk-changes/creating-a-new-cardholder-bulk-change/default-floors.md).

# Change Default Floors

1. Select **Default Floors**.

   The Change Default Floors pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-09776355720a8af7b36186016ca81d634482bb3e%2Fchbulkchange_changedefaultfloors.png?alt=media)
2. Select the Default Floors that need adding to and/or removing from the cardholders, by clicking the **Select Default Floors** button in the appropriate section on the screen, (i.e. either in the "+Set/Update these Default Floors" section or the "-Remove Default Floors from these Elevator Groups" section).

   The Set/Update Default Floors pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-fef0a256db09405a0488d7190978299758ca1778%2Fchbulkchange_setupdatedefaultfloors.png?alt=media)
3. Click on the Default Floor drop-down box beside the Elevator Group you want to assign a Default Floor to.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-dd70ea5e87471540a0f4b214d37ea5b66e8d147d%2Fchbulkchange_setupdatedefaultfloorsdropdown.png?alt=media)
4. If necessary, search for Access Zone you want by entering characters in the Search field.
5. Select the appropriate Access Zone from the drop-down list.
6. Repeat Steps 3. to 5. for each Elevator Group you want to assign a Default Floor to.
7. Click the **Add** button.

   The configured default floors show in the bottom grid.
8. Click the **Add Selection** button.

   The Set/Update Default Floors pop-up closes and each of the selected Access Zone(s) now appear on the Change Default Floors pop-up.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-4a62d6cd08309cf05fb96fd20902e2d4f56e15da%2Fchbulkchange_changedefaultfloors_populated.png?alt=media)
9. Default Floors are invalid if cardholders don’t have access to them.

   Tick the **Remove invalid default floors** checkbox if you want invalid default floors to be removed from the cardholders selected in the bulk change.
10. Click the **OK** button.

    The Change Default Floors pop-up closes.


---

# 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/command-centre-client/configuring-command-centre/administration/bulk-changes/creating-a-new-cardholder-bulk-change/default-floors.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.
