> For the complete documentation index, see [llms.txt](https://docs.geopard.tech/geopard-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geopard.tech/geopard-tutorials/nl/producttour-webapp/integratie-met-john-deere-operations-center/3.-verbinden-met-john-deere-organisaties.md).
# 3. Verbinden met John Deere-organisaties
Koppel John Deere-organisaties om gegevens te importeren, exporteren en delen te automatiseren.
2\. Verbinden met de John Deere-organisatie
2.1 Als de John Deere-organisatie is uitgeschakeld (de **naam heeft een grijze kleur**), dan moet de gebruiker toegang toevoegen tot John Deere Operations Center. De gebruiker moet op een **Verbinden** koppeling klikken.
2.2 Na het klikken op de **Verbinden** koppeling wordt de gebruiker doorgestuurd naar John Deere Operations Center.
2.3 In John Deere Operations Center kan de gebruiker toegang toevoegen tot de organisatie. **Controleer of de naam van de organisatie in de keuzelijst correct is.**
2.4 Klik vervolgens op de gebruiker op de **Opslaan** knop om de wijzigingen toe te passen.
2.5 Na het toevoegen van de toegang kan de gebruiker werken met een ingeschakelde organisatie in GeoPard.
2.6 Na het selecteren van organisaties kan de gebruiker ermee werken in GeoPard.
---
# 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.geopard.tech/geopard-tutorials/nl/producttour-webapp/integratie-met-john-deere-operations-center/3.-verbinden-met-john-deere-organisaties.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.
