> 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/product-tour-web-app/john-deere-operations-center-integration/data-sharing-options/2.-problem-solving-of-staff-member-sharing.md).
# 2. Problem-solving of "Staff Member" sharing
Fix common John Deere staff sharing issues that block access or data sync.
## 2.1 If the staff member can NOT connect the shared organization to the GeoPard app.
1. The staff member sees the popup about grant permissions.
2. The staff member should go to the "Setup" >> "Team" page (or ) and check the "Access" tab.
3. The "Share Organization Data with Connected Software Companies" option should be available.\
If this option is not available, then the staff member should notify the owner about it to fix the access.
## 2.2 If the staff member can NOT see fields of the shared organization in the GeoPard app.
1. If the staff member does not see fields in the GeoPard app.
2. The staff member should go to the "Setup" >> "Team" page (or ) and check the "Access" tab.
3. The "Locations" access level should be 3.\
If this option is not available, then the staff member should notify the owner about it to fix it.
4. The fields should be available in the shared organization in the GeoPard app.
---
# 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/product-tour-web-app/john-deere-operations-center-integration/data-sharing-options/2.-problem-solving-of-staff-member-sharing.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.
