> For the complete documentation index, see [llms.txt](https://help.fielddoc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fielddoc.org/help-center/account-management/organization-management/understanding-workspace-access-and-record-sharing-in-fielddoc.md).

# Understanding Workspace Access and Record Sharing in FieldDoc

### User accounts are configured to one organization

Every user in FieldDoc is a **member of a single organization** (the one that employs you). Each basic organization has a corresponding workspace (Standard accounts may have multiple workspaces to separate and organize data within their organization). 

<figure><img src="https://3275504260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKGb6YoxmTSofsW7jXvU0%2Fuploads%2F5fDIK5NP7ZUWeOXOKOuU%2FScreenshot%202026-10-14%20at%209.56.25%E2%80%AFAM.png?alt=media&amp;token=2af594c3-2934-4b4a-99b9-e3a9c6e05598" alt=""><figcaption></figcaption></figure>

### Workspaces organize a container of records

Because so much work is done through collaboration, users from other organizations can be made an admin of your workspace via the Workspace settings. This allows contractors or partners to do work on behalf of your organization in your organization's workspace. All workspace admins can open up a workspace and then access all of the records and pacts in the workspace to create, edit, or delete records.&#x20;

<figure><img src="https://3275504260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKGb6YoxmTSofsW7jXvU0%2Fuploads%2FrqfJgirlrw8Iq3ORxt1g%2FScreenshot%202026-10-14%20at%209.54.27%E2%80%AFAM.png?alt=media&amp;token=a9a1b039-933f-404f-832e-3ef219f35ef8" alt=""><figcaption></figcaption></figure>

### Share folders or records to isolate access

There is also an option to **share individual pacts or records**. If you’re not a member of the other organization’s workspace, but you can access the pact and, while you are in it, create, edit, or delete records.

<figure><img src="https://3275504260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKGb6YoxmTSofsW7jXvU0%2Fuploads%2F66Iyei4y4eh03y1J2ld3%2FScreenshot%202026-10-14%20at%209.53.42%E2%80%AFAM.png?alt=media&amp;token=ec6abe07-34c1-48f6-8aca-ef7c0dc440e6" alt=""><figcaption></figcaption></figure>


---

# 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://help.fielddoc.org/help-center/account-management/organization-management/understanding-workspace-access-and-record-sharing-in-fielddoc.md?ask=<question>&goal=<user_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.