> 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/site-installation/hardware/creating-controllers/creating-a-controller-7000-single-door.md).

# Creating a Controller 7000 Single Door

### Introduction

The Controller 7000 Single Door is a processing board for an intruder alarm and access control system that can control a single door.

***

### Configuration

To create a new Controller 7000 Single Door, perform the following procedure in Gallagher Configuration Client:

1. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. **Right click** and select **New\...Controllers** > **Controller 7000 Single Door**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Event Response** tab, and configure as required.

   For further detail see [Event Response tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/event-response-tab.md).
5. By default, continuous tamper alarms will be generated if the Controller is tampered with, (i.e. a 'Front Tamper' alarm if the cover is removed, or a 'Rear Tamper' alarm if the Controller is removed from the wall).

   Do you want to prevent tamper alarms from happening?

   <table><thead><tr><th width="67">If...</th><th>then...</th></tr></thead><tbody><tr><td>no,</td><td>go to Step 6.</td></tr><tr><td>yes,</td><td><ol><li>Click the <strong>Status and Overrides</strong> tab.<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-056508fe8cc08732ae886783d3614c98690d38d9%2Fcontroller7000_status%26overridestab.png?alt=media" alt=""></li><li>Tick the <strong>Disable Front Tamper</strong> and/or <strong>Disable Rear Tamper</strong> checkbox(es).<br><br><strong>Note:</strong> The Controller 7000 Single Door has a <strong>Disable Front Tamper</strong> and a <strong>Disable Rear Tamper</strong> checkbox so the tampers can be enabled/disabled independently.</li></ol></td></tr></tbody></table>
6. Click each tab in turn and configure the Controller properties as required:

<details>

<summary>Setup tab</summary>

1. Click the **Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1895ca23af18f2bdb9ea3ba3fbfdd2867d0d734a%2Fcontroller7000_setuptab.png?alt=media)
2. Select the **Controller Type** from the drop-down list, (i.e. either **RS-485** if the physical Controller supports RS-485 devices, or **Wiegand** if the physical Controller supports Wiegand Reader).

   **Note:** If Wiegand is selected, the **HBUS Devices** tab will disappear from the list of tabs on the left.
3. The **Time Zone** section of the screen is automatically populated with the same time zone the Command Centre Server is in.
4. If you require another city/time zone, you can select one from the drop-down **Quick list**, and the POSIX time zone string in the **Actual value** field will be updated.

   The formatting rules for time zone strings are as follows:

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Time Zone string format is:</strong></p><p>{STDName}{Offset}[{DSTName}{Offset},{Start rule},{End rule}]</p><p>Offsets are in Americocentric form, (i.e. multiplied by -1 in order to make US timezones positive).</p><p>The Start and End rules can be omitted if there is no daylight saving. The rules can be written in one of the following three formats:</p><ul><li><strong>Jn</strong> - where n = {1-365} (Day of year, but Feb 29 never counted)</li><li><strong>n</strong> - where n = {0-365} (Day of year)</li><li><strong>Mm.w.d</strong> - where m=month {1-12}, w=week of month {1-5} (5=last), d=day of week {0(Sun)-6(Sat)}</li></ul><p>These can be followed by an optional changeover time in format:</p><p>/hh[:mm[:ss]] - default is 2:00:00.</p><p>If the daylight savings offset is omitted, then one hour more than the standard offset is assumed.</p><p><strong>Example:</strong></p><p>New Zealands timezone string is: NZST-12NZDT,M10.1.0,M3.3.0, which means New Zealand is 12 hours ahead of GMT, our daylight savings (of one hour) starts on the first Sunday of October and finishes on the third Sunday of March, both at the default time of 2am.</p></div>
5. The **Calendar** drop-down list contains a list of all the special calendars configured in the system for the operator's division. One special calendar may be assigned to each Controller in the system.

   By default, no special calendar will be assigned to the Controller. However, if you require one to be assigned, select the appropriate special calendar from the drop-down list.

   This Controller will use both the special calendar selected as well as the default calendar for its scheduling operations. The default calendar provides cycle and special day assignments, while the special calendar provides special day assignments only, with the possibility of overriding special day settings from the default calendar.

   **Note:** Refer to [Creating a Special Calendar](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/calendars/creating-a-special-calendar.md) for further detail about special calendars.
6. The **Hardware** section allows you to alter the devices used as required.

   The options available will depend on the selection you made in the **Controller Type** field, (i.e. either RS-485 or Wiegand), as follows:

   <table><thead><tr><th width="121">If...</th><th>then...</th></tr></thead><tbody><tr><td>RS-485,</td><td>select the correct RS-485 Bus type from the drop-down list for the devices connected to the Controller.<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-39dfe4562da605229dc179afa17a9e669b05d580%2Fcontroller7000_setuptab_rs485bus.png?alt=media" alt=""></td></tr><tr><td>Wiegand,</td><td>select the appropriate Wiegand Reader from the drop-down list.<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-67ed80962017707687dbef97f467ad4c4d8b7e06%2Fcontroller7000_setuptab_wiegand.png?alt=media" alt=""></td></tr></tbody></table>
7. If required, tick the **Turn off run LED when cover is in place** checkbox.
8. The **DipSwitch 1 controls the diagnostic web interface** checkbox should be ticked if requested by Gallagher Technical Support. Otherwise, leave this option unticked.

   **Important:** If Dip Switch 1 is to be used to control the diagnostic web interface, Dip Switch 1 needs to be physically ‘ON’ on the Controller as well as this checkbox being enabled.
9. The **Logging** section allows you to configure the verbosity of diagnostic logs from this Controller which are written into the Command Centre log file. The log level can be changed to a value from **Off**, (i.e. least verbose) to **Trace**, (i.e. most verbose).

</details>

<details>

<summary>Power tab</summary>

1. Click the **Power** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2f862fd418af289d1ba5006e5cb4ea1de007f8ee%2Fcontroller7000_powertab.png?alt=media)
2. Select the appropriate **Power type** from the drop-down list.

   **Notes:**

   * A power type must be selected otherwise a pop message will display asking you to select one when you click **Apply** or **OK**.
   * If you select PoE+ or PoE the **Battery connected** option becomes enabled, but it remains disabled if you select DC.
3. If you selected PoE+ or PoE, tick the **Battery connected** checkbox if required.
4. The **Low Power threshold** field can be altered to set the level at which a low voltage alarm will be generated for the Controller.

</details>

<details>

<summary>Network tab</summary>

1. Click the **Network** tab.

   The **General** sub-tab displays by default.

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

   **Note:** The **802.1x** sub-tab enables sites to configure a Controller 7000 Single Door for 802.1x. See [Configuring a Controller 7000 or 7000 Single Door for 802.1x](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/configuring-a-controller-7000-or-7000-single-door-for-802-1x.md) for further instructions.
2. Enter the **MAC Address** for the Controller.

   The MAC Address for each Controller is stuck to the actual Controller PCB.

   **Note:** A MAC address range is included in your license file and will be checked against when a MAC address is saved here. If you receive a "MAC address out of range" error message, check your license file to see what range is valid.
3. Entering the **Serial Number** of the Controller is optional and can be found printed on one of the Controller labels.
4. Click the radio button for the appropriate **Network Method**, i.e. either **Automatic (DHCP)**, **Manual** or **OneLink**.

   **Automatic (DHCP)** is the preferred method for controllers connected on the local network, but if you select **Manual** the **Controller Address** section changes as shown below:

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

   The **OneLink** method utilises Gallagher Cloud Services to enable Controller 7000s to connect to the on-premises Command Centre Server over the internet. See [OneLink Configuration](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/onelink-configuration.md) for further instructions.
5. Enter the **IP Address**, (i.e. TCP-IP Address), **Subnet** and **Gateway** information for the Controller.

   This information will be provided by the IT Department for the organisation, or the IT provider of the network.

   **Note:** By default, the **Subnet** and **Gateway** fields are populated with the first subnet mask and gateway from one of the server's ethernet adaptors with a non-zero gateway.

   If there is no IT support for this site, and it is a localised and dedicated LAN built for Command Centre, there are some standards that you can apply to the configuration of the Controllers, as described next:

   <table><thead><tr><th width="133">Configuration Parameter</th><th>Description</th></tr></thead><tbody><tr><td>IP Address</td><td>The Internet Assigned Numbers Authority (IANA) has reserved the following three blocks of TCP-IP address space for private networks:<br>Class A From 10.0.0.0 to 10.255.255.255<br>Class B From 172.16.0.0 to 172.31.255.255<br>Class C From 192.168.0.0 to 192.168.255.255<br>These TCP-IP addresses have been set aside specifically for use when it is not necessary (or desirable) for the attached devices to be available on the Internet. If one of these TCP-IP addresses were accidentally broadcast on the Internet they would be ignored by the routing firewall server and would cause no conflict issues.<br>The first block is a single Class "A" network number, the second block is a set of 16 contiguous Class "B" network numbers, and the third block is a set of 256 contiguous Class "C" network numbers.<br><br><strong>Note:</strong> Each device, (i.e. Computer, Printer, Controller) on the localised LAN must have a unique TCP-IP address. Each address used must however be in the same Subnet Mask range.<br>This means as an example, if you use the Class "B" TCP-IP address range, each TCP-IP address assigned to the localised LAN must start with 172.16 and then be unique, (e.g. 172.16.0.1, 172.16.0.2, 172.16.0.3, 172.16.0.4, etc.)</td></tr><tr><td>Subnet</td><td>There are default Subnet Mask settings for the three class categories:<br>Class A From 10.0.0.0 to 10.255.255.255<br>Default Subnet Mask is 255.0.0.0<br>Class B From 172.16.0.0 to 172.31.255.255<br>Default Subnet Mask is 255.255.0.0<br>Class C From 192.168.0.0 to 192.168.255.255<br>Default Subnet Mask is 255.255.255.0<br>Use the associated Subnet Mask appropriate for the TCP-IP class used. The Subnet Mask differentiates between the network and client parts of the TCP-IP address. The "255's" identify the network section and the "0's" identify the clients.<br>For a Class "B" TCP-IP address the network identification numbers are "172.16" and will be identical for each TCP-IP address on that network. The following two numbers of the TCP-IP address uniquely identify each device on the network.</td></tr><tr><td>Gateway</td><td>Gateway settings when used in general LAN configurations provide a path to a different network environment. In a localised LAN environment for Gallagher there is no physical connection to a different network, so the Gateway setting is ineffective.<br>On single Subnet networks, it is recommended the Gateway information be set exactly as the TCP-IP address used, or alternatively 0.0.0.0</td></tr><tr><td>Enable custom DHCP</td><td>This checkbox allows sites to use their own Dynamic Host Configuration Protocol (DHCP) service to assign IP addresses to their controllers automatically, without physically needing to be at the controller.<br>See <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/configuring-a-controller-for-dhcp.md">Configuring a Controller 6000 for DHCP</a> for further detail.</td></tr></tbody></table>
6. Click the radio button for the appropriate **Server Address**, (i.e. either **Default Server Address** or **Custom Server Address** ).

   If you selected **Automatic (DHCP)** for the "Network Method", and you select **Custom Server Address**, this section will change as shown below:

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

   If you selected **Manual** for the "Network Method", and you select **Custom Server Address**, this section will change changes as shown below:

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ba84d4309ea4cb51aeb10548cc61854a995aa7f9%2Fcontroller6000_networktab_customserveraddress_manualnwmethod.png?alt=media)
7. If this Controller is separated from the Server by a firewall, so it can still contact the Command Centre Server, enter the IP Address.
8. Controllers must be able to make use of Domain Name Servers (DNS) in disaster recovery situations, especially where backup servers reside on different subnets.

   See [Configuring DNS Servers for Controllers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/configuring-dns-servers-for-controllers.md) for the procedure.
9. Controller 7000s Single Door support both IPv4 and IPv6. A Controller 7000 that needs to communicate with IPv4 external systems must be assigned IPv4 addresses as per existing configuration procedures.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>To assign an IPv6 address additional to IPv4:</strong></p><ol><li>The only supported method of address allocation for the Controller is an auto configuration via router advertisements. The Controller will only accept IPv6 auto configuration if it is either already configured for IPv6 communication or the Controller was booted with DIP switch 2 on.</li><li>Check the <strong>Enable IPv6</strong> checkbox.<br>The <strong>Enable IPv6</strong> section changes as shown below if you selected <strong>Manual</strong> as the "Network Method" above:<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-cf3f7bace6ee9748c97ff5ee6062f41d7300121d%2Fcontroller6000_networktab_enableipv6.png?alt=media" alt=""></li><li><p>Click either the <strong>Network Prefix</strong> or <strong>Address</strong> radio button and enter appropriate details.</p><ul><li><strong>Network Prefix</strong> contains a pre-populated network prefix combo field containing all subnet prefixes available at the Command Centre server machine. The interface identifier of the Controller is pre-populated based on the entered MAC address.</li><li>The <strong>Address</strong> field is free text field to provide complete IPv6 address instead. The given address shall be from the list of IPv6 addresses assigned to the Controller through the auto-configuration process. Hostname is not supported here.</li></ul></li></ol></div>

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>To assign only an IPv6 address:</strong></p><ul><li>IPv4 address can be NULL in this case.</li><li>DIP switch 2 should be ON.</li><li>Reset is the same as above.</li></ul></div>

   **Note:** A document providing further technical information about IPv6 ( **Gallagher Command Centre IPv6 Support.pdf** ) is available in the `'Documentation'` directory of the Command Centre installation files.
10. Click the **Enable NAT** checkbox if your site wants Command Centre to communicate with multiple Controllers on different networks.

    Selecting **Enable NAT** expands the section as shown below:

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

    Refer to [Configurable Ports - NAT Solution](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/configurable-ports-nat-solution.md) for further detail.

</details>

<details>

<summary>Outputs tab</summary>

1. Click the **Outputs** tab.

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

   This tab allows you to link a maximum of two outputs to the Controller to activate another device, (e.g. alarms, light switching, doors unlocking).
2. For the appropriate Output, click within the edit box.

   From the displayed drop-down menu, select the output name.

</details>

<details>

<summary>Inputs tab</summary>

1. Click the **Inputs** tab.

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

   This tab allows you to link inputs to the Controller. The number of inputs available will depend on what **Controller type** you selected on the **Setup** tab, (i.e. a maximum of six inputs if you selected RS-485, or a maximum of five inputs if you selected Wiegand).
2. If you wish to use an input as the cabinet tamper, tick the **Use Input 1 for cabinet tamper** checkbox (which disables the Input 1 field).

   **Note:** If you do tick this option, the **Disable Front Tamper** and **Disable Rear Tamper** checkboxes on the Status and Overrides tab are replaced with a **Disable Cabinet Tamper** checkbox.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a5157e3a1830a015b23432b56357ab1c4bfc284f%2Fcontroller7000_status%26overridestab2.png?alt=media)
3. For the appropriate Input, click within the edit box.

   From the displayed drop-down menu, select the input name.

   **Note:** If Input 1 is already in use, ticking the **Use Input 1 for cabinet tamper** checkbox will generate the following message:

   *"Input is assigned as a tamper input. Please remove the first input from this controller."*

</details>

<details>

<summary>EOL Resistors tab</summary>

This tab allows you to configure End-of-line (EOL) resistances for the Controller.

For further detail see [Configuring EOL Resistors for devices](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/configuring-eol-resistors-for-devices.md).

</details>

<details>

<summary>HBUS Devices tab</summary>

This tab allows you to assign HBUS devices to the Controller.

For further detail see [Configuring HBUS Devices](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/configuring-hbus-devices.md).

</details>

<details>

<summary>Software tab</summary>

This tab allows you to assign device software to the Controller.

Refer to either [Assigning Device Software to devices](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/device-software/assigning-device-software-to-controllers.md), or [Upgrading Multiple Controllers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/device-software/upgrading-multiple-controllers.md) if you are upgrading the firmware on multiple Controllers.

</details>

7. Click the **Cameras** tab if you want to associate a DVR Camera(s) with this Controller.

   For further details regarding the **Cameras** tab, see [Cameras](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/cameras-tab.md).
8. Click the **Icons** tab if you want to change the Icon Set for this Controller.

   For further details regarding the **Icons** tab, see [Icons](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/icons.md).
9. Server to Controller, or Inter-controller offline monitoring can be configured from the **Offline Monitoring** tab.

   See [Configuring Offline Monitoring](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/configuring-offline-monitoring.md) for further detail.
10. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Controller.

    For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
11. Click the **Notes** tab if you want to add a note(s) about this Controller.

    For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
12. Click **OK** to exit and save your changes.

    Click **Cancel** to exit without saving your changes.

    Click **Apply** to save your changes and stay in this window.

### Result

A Controller 7000 Single Door has been created. The Controller name now displays within the **Hardware** List Window.

***

### Hints

{% hint style="info" %}
**Re-sync Databases**

Performing a **Re-sync Databases** action on a Controller (via the Controller context menu), deletes the card database at the Controller and automatically re-populates it.
{% endhint %}

{% hint style="info" %}
**Purge Pending Messages**

Performing a **Purge Pending Messages** action on an offline Controller (via the Controller context menu), will clear the queue of outgoing messages and bring the Controller online. Operators require either the "Advanced User" or "Maintenance Override" privilege in the division of the Controller to perform this action.

**WARNING:** The Purge Pending Messages action is only intended to be used on an offline Controller that will be restarted with Dip Switch 2 active. Dip Switch 2 indicates to the server that the Controller wants all configuration data, if the Controller is only offline due to network connectivity and the message queue is cleared then important configuration messages may be purged with this tool.
{% endhint %}


---

# 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/site-installation/hardware/creating-controllers/creating-a-controller-7000-single-door.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.
