> 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/zwapgrid-managed-connection.md).
# Zwapgrid-managed Connection
***
A Zwapgrid-managed connection uses an application configuration supplied and maintained by Zwapgrid. This setup remains in use for Accounting Systems that do not yet expose System Settings and for some existing integrations.
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 system supports it. Zwapgrid-managed and client-managed setups are not interchangeable options for every system; follow the relevant [System Setup Guide](/client-portal/systems/setup-guides.md).
### How It Works
When Your Customer connects a system, they share access through Zwapgrid's secure infrastructure. Depending on the Accounting System, this can involve:
* An application client registered and maintained by Zwapgrid.
* Another vendor-specific connection method maintained by Zwapgrid.
You do not create a separate System Setting for this setup. If System Settings later become available for the system, coordinate the migration with Zwapgrid before changing a production integration.
***
### Example: Visma Spiris
For an existing Zwapgrid-managed Visma Spiris integration, previously known as Visma eAccounting, Your Customer authorises access within Spiris. Zwapgrid's application configuration is then used to exchange the permitted data through API.1.
Your Customer will see the following:
Zwapgrid-managed connection flow.
---
# 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/zwapgrid-managed-connection.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.
