> 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/build-a-portfolio/record-management/can-records-exist-in-two-workspaces.md). # Can records exist in two workspaces? Created: July 21, 2026 Records can exist in two workspaces by using the **Share** function. ## Share Records Across Workspaces FieldDoc’s sharing function allows you to share existing records with another workspace. To share multiple records at once, you can share the folder that contains them. Sharing a folder does **not** automatically share records added to that folder later. New records must be shared separately. ### Part 1: Share the records 1. Open the workspace that contains the original folder. 2. Open the folder and click **Share** in the upper-right corner. 3. Enter the email address of a FieldDoc user who has access to the target workspace. 4. Click **Send**. > **Have feedback?** Would selecting a target workspace be more helpful than entering a user’s email address? Let us know if you would like to see this improvement considered for future development. ### Part 2: Organize the records in the target workspace 1. Open the target workspace. 2. In the **Activities** section, create a folder for the shared records, if needed. 3. Open the **Shared with me** view. 4. Open the shared folder. 5. Click **Select** and choose the records you want to organize. 6. Click **Move to folder** and select the destination folder. The records are now available and organized in the target workspace. Any edits made to a shared record will appear in both workspaces. Remember to repeat this process for any new records that need to be shared. {% embed url="" %} --- # 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/build-a-portfolio/record-management/can-records-exist-in-two-workspaces.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.