> 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/lva/produkta-apskats-timekla-lietotne/john-deere-operations-center-integracija/3.-savienot-ar-john-deere-organizacijam.md).
# 3. Savienot ar John Deere organizācijām
Savienojiet John Deere organizācijas, lai importētu, eksportētu un automatizētu datu koplietošanu.
2\. Savienojieties ar John Deere organizāciju
2.1 Ja John Deere organizācija ir atspējota ( **nosaukums ir pelēkā krāsā**), tad lietotājam jāpievieno piekļuve John Deere Operations Center. Lietotājam jānoklikšķina uz **Savienot** saites.
2.2 Pēc tam, kad noklikšķināts uz **Savienot** saites, lietotājs tiks pāradresēts uz John Deere Operations Center.
2.3 John Deere Operations Center lietotājs var pievienot piekļuvi organizācijai. **Pārbaudiet, vai organizācijas nosaukums nolaižamajā sarakstā ir pareizs.**
2.4 Pēc tam lietotājam jānoklikšķina uz **Saglabāt** pogas, lai piemērotu izmaiņas.
2.5 Pēc piekļuves pievienošanas lietotājs var strādāt ar iespējotu organizāciju GeoPard.
2.6 Pēc organizāciju atlasīšanas lietotājs var strādāt ar tām 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/lva/produkta-apskats-timekla-lietotne/john-deere-operations-center-integracija/3.-savienot-ar-john-deere-organizacijam.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.
