> For the complete documentation index, see [llms.txt](https://docs.zwapgrid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zwapgrid.com/client-portal/systems/connection-management.md). # Connection Management Connection management describes who owns and maintains the vendor application used when Your Customer connects an Accounting System. For new integrations, use a [client-managed connection](/client-portal/systems/client-managed-connection.md) with [System Settings](/client-portal/systems/system-settings.md) whenever the Accounting System supports it. Your organisation owns the vendor application and controls its credentials, permissions, and lifecycle. Zwapgrid is moving toward this as the standard model across all systems. A [Zwapgrid-managed connection](/client-portal/systems/zwapgrid-managed-connection.md) remains in use for systems that do not yet expose System Settings and for some existing integrations. It is the current fallback or an agreed exception, rather than an interchangeable setup choice. Follow the relevant [System Setup Guide](/client-portal/systems/setup-guides.md) to see which process currently applies. Contact before changing the model for an existing production integration. --- # 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://docs.zwapgrid.com/client-portal/systems/connection-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.