> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/web-chat-widget/chat-widget-settings.md). # Chat Widget Settings The **Settings** section allows you to manage the basic configuration of your chat widget, control where the widget can be used, and define how conversations are created, managed, and reopened. The Settings section contains three tabs: 1. **General** 2. **Conversation Policy** 3. **Identity Verification** This document covers the **General** and **Conversation Policy** settings. ### 1. General Settings The **General** tab contains the basic configuration and security settings for your chat widget. #### Widget Name The **Widget Name** is used to identify the chat widget within your account. You can enter a new name or update the existing name whenever required. #### Allowed Origins **Allowed Origins** define the websites where your chat widget is permitted to load. Enter the website URL where you want to use the widget and click **Add Origin**. You can add multiple websites by adding each website as a separate origin. You can also remove an existing origin using the **Delete** icon. > **Note:** When you save the settings, the complete list of allowed origins will be replaced with the list currently displayed in the settings. #### Widget Status The **Status** option controls whether the chat widget is active or paused. * **Active:** The widget can load and function normally on your website. * **Paused:** The widget will stop authenticating and will no longer load on your website. Use this option when you temporarily want to disable the widget without deleting it. #### Widget Key The **Widget Key** is a public key used in the embedded code snippet when adding the chat widget to your website. You can use the **Copy** icon to quickly copy the widget key when required. #### Widget Secret The **Widget Secret** is an HMAC key used by your backend to securely sign visitor information, such as email addresses and phone numbers. Since the widget secret is sensitive information: * Keep it securely on your server. * Do not add it directly to your website's frontend. * Do not expose it in publicly accessible page source or client-side code. You can use the **View** icon to display the secret and the **Copy** icon to copy it. #### Rotate Secret If required, you can use **Rotate Secret** to generate a new widget secret key. After rotating the secret, make sure your backend configuration is updated with the new value. ### Danger Zone The **Danger Zone** contains the option to permanently delete the chat widget. #### Delete Widget Click **Delete Widget** only when you are sure that you no longer need the widget. Deleting the widget will: * Stop the widget from loading on your website. * Permanently remove the widget configuration. > **Warning:** This action cannot be undone. Make sure you want to permanently delete the widget before proceeding. #### Save Changes After making changes to the General settings, click **Save Changes** to apply the updated configuration. ## 2. Conversation Policy The **Conversation Policy** settings control how conversations are created, managed, and reopened for returning visitors. The main settings include: * Multiple Conversations * Open Conversations Per Visitor * Reopen Window ### Multiple Conversations The **Multiple Conversations** option determines whether a visitor can have more than one conversation. #### Disabled When this option is disabled, each visitor can have only **one conversation thread**. All messages from the visitor are maintained within the same conversation. #### Enabled When enabled, a visitor can create multiple separate conversations. This can be useful when visitors want to discuss different topics without mixing them into the same conversation. ### Open Conversations Per Visitor This setting defines the maximum number of conversations a visitor can keep open at the same time. For example, if the limit is set to **5**, a visitor can have up to five open conversations simultaneously. Once the visitor reaches this limit, they cannot start another conversation until one of their existing conversations is closed. ### Reopen Window The **Reopen Window** determines how long a closed conversation can be reopened when the visitor returns. For example, if the reopen window is set to **48 hours**: * A closed conversation can be reopened if the visitor returns within 48 hours. * If the visitor returns after 48 hours, a new conversation will be created. #### Reopen Window Set to 0 If the reopen window is set to **0**, reopening is disabled. In this case, a returning visitor will always start a new conversation. ### Conversation Selection Behavior When a visitor returns: 1. The visitor will first continue with their **newest open conversation**. 2. If there is no open conversation, a recently closed conversation may be reopened based on the configured **Reopen Window**. 3. If the visitor has already reached the maximum number of open conversations, they cannot start another conversation until one of the existing conversations is closed. ### Save Conversation Settings After configuring the required conversation policies, click **Save Changes** to apply the settings. {% embed url="" %} --- # 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://helpdocumentation.gitbook.io/user-documentation/web-chat-widget/chat-widget-settings.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.