> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/smb/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/smb/test-and-active/publish-configuration-to-controller.md). # Publish/Refresh Configuration Changes made within the Installer Portal do not take effect until they are published to the Controller with the [**PUBLISH** ](#publishing-configuration-to-the-controller)or [**REFRESH** ](#refreshing-the-controller-configuration)button. The PUBLISH button displays when there are pending hardware changes; the REFRESH button displays at all other times to allow you to ensure the Controller configuration is up to date (e.g. if you have made a non-hardware site change). When publishing/refreshing configuration to the Controller, doors will revert to their original schedule regardless of whether the customer has performed an override. For example, if the customer has overridden the schedule to Free, and then a Lock Door override is performed, the door will lock and the override will be lost. Once changes have been published to the Controller, there is no way to restore to a previously published version. To revert the site configuration to how it was when it was last published, select DISMISS CHANGES under **Pending Changes**. **Note:** Configuration can only be published/refreshed when the Controller is online. ### Publishing configuration to the Controller 1. All changes appear in the sidebar to the right under **Pending Changes**. **Note:** If no changes have been made since the last publish, the 'Pending Changes' section does not display. 2. Select the floating **PUBLISH** button to publish the changes. **Note:** If the Controller is offline, the button will be disabled. If there are no pending hardware configuration changes, the '[REFRESH](#refreshing-the-controller-configuration)' button shows instead. 3. When **PUBLISH** is selected, a pop-up window will appear asking you to confirm you want the changes published. Select **Publish Changes**.\ **Note:** For all newly-installed sites, when the Controller comes online, it will immediately start downloading new firmware.\ If the firmware is still downloading when you attempt to publish the changes, a warning will appear. If changes are published while the download is not completed, the download will restart from the beginning. 4. After the configuration has been published, a small confirmation displays. ### Refreshing the Controller configuration If you have not made any hardware changes, but need to update the Controller's configuration anyway (e.g. you changed the site's timezone), you can use the 'REFRESH' button. 1. Select the floating **REFRESH** button to publish the current configuration to the Controller.\ **Note:** If the Controller is offline, the button will be disabled. If you have pending hardware configuration changes, the '[PUBLISH](#publishing-configuration-to-the-controller)' button shows instead. 2. When **REFRESH** is selected, a pop-up window will appear asking you to confirm you want the Controller to be updated. Select **Yes**.\ **Note:** For all newly-installed sites, when the Controller comes online, it will immediately start downloading new firmware.\ If the firmware is still downloading when you attempt to refresh the configuration, a warning will appear. If configuration is refreshed while the download is not completed, the download will restart from the beginning. 3. After the configuration has been refreshed, a small confirmation displays. --- # 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/smb/test-and-active/publish-configuration-to-controller.md?ask=&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.