> For the complete documentation index, see [llms.txt](https://partner-docs.covergenius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://partner-docs.covergenius.com/offers/services/xcover/policy-management.md). # Policy Management Most users will manage policies on XCover.com After booking and over the course of using a policy, users may need to manage their policy, to view and reference their policy inclusions, limits, or terms and conditions, and to update their account information. In most instances, this is performed on [XCover.com](https://www.xcover.com/en/login). Partners may wish to include a link to this page in their experience, and often a specific policy URL will be appropriate to include, such as: * Claims:\ [https://xcover.com/en/account/claims/fnol?bookingID=1ABCD-VWXYZ-INS](https://staging.xcover.com/en/account/claims/fnol?bookingID=7XPGF-LMCQK-INS) * Modification:\ * Certificate of Insurance (COI):\ [https://xcover.com/en/coi/1ABCD-VWXYZ-INS](https://xcover.com/en/modify/1ABCD-VWXYZ-INS) * Policy Disclosure Statement / Policy Wording (PDS):\ [https://xcover.com/en/pds/1ABCD-VWXYZ-INS](https://xcover.com/en/modify/1ABCD-VWXYZ-INS) Users will also need to have created an account before using these links.\ In most cases, users will receive an account creation email containing a specific login URL shared with them after booking, usually via a policy confirmation email. --- # 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://partner-docs.covergenius.com/offers/services/xcover/policy-management.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.