> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/integrations/file-export.md).

# File export

File each project's completed emails, meeting minutes, RFIs, submittals, field reports, documents and drawings into its folder on your file server or in Egnyte, automatically.

File export keeps each project's folder complete without anyone filing by hand. Cogram copies a project's completed items into the folder you link, on your file server or in Egnyte, and keeps adding new ones as they are completed.

## Prerequisites

* A destination is connected:
  * **File server:** see [Connecting your file server](https://docs.cogram.com/integrations/connecting-your-file-server.md).
  * **Egnyte:** see [Connecting Egnyte](https://docs.cogram.com/integrations/connecting-egnyte.md).
* To set firm rules or link any project, you are an administrator. Project owners and leads can link their own projects.

## When to use this

* Your project record lives on a file server or in Egnyte, and the team files items there twice.
* You want RFIs, submittals and minutes in the right project folder as soon as they are complete.
* You are onboarding many projects and want to link them in one pass.

## How it works

* **One folder per project.** A folder can belong to only one project.
* **Only completed items are filed.** A meeting is filed once its minutes are ready, an RFI once it has an answer, a transmittal once it is closed.
* **Cogram only adds files.** It never overwrites, renames or deletes anything in your folders.
* **Each item is filed once.** Unlinking and linking the folder again does not file the same items a second time.
* **New items only, by default.** A new link files items completed from that day on. You can choose to include past items as well.

## Set up File export

Go to [Organization Settings → Integrations → File export](https://app.cogram.com/dashboard/settings/admin/integrations#file-export). Until a project is linked, the page shows a checklist, **Set up file export**, with three steps. Each step opens once the one before it is done.

### 1. Choose where to file

* **Egnyte:** select **Connect filing account** and sign in as the Service Account. See [Connecting Egnyte](https://docs.cogram.com/integrations/connecting-egnyte.md#connect-the-service-account).
* **File server:** select **Set up the connector**. See [Connecting your file server](https://docs.cogram.com/integrations/connecting-your-file-server.md).

### 2. Choose what to file

1. Select **Edit defaults**.
2. Under **When a project is linked**, select **New items only** or **Also file past items**.
3. Under **Item types**, turn on each type to file. For each type, choose its folder inside the project's folder, for example `04 Construction/RFIs`. Cogram uses folders that exist and creates the ones that are missing.
4. If both Egnyte and a file server are connected, choose where new links go under **New links file to**.
5. Optional: select **Show preview** to see how each project's folder looks after filing.
6. Select **Save defaults**.

The defaults apply when a project is linked. If you later change a type's folder, Cogram offers **Apply new folders to** the linked projects. Past files stay where they are, and new files go to the new folders.

### 3. Link projects to folders

1. Select **Link projects**.
2. Next to **Projects folder**, select **Choose folder** and choose the folder that holds your project folders, for example `/Shared/Projects`. Cogram matches its subfolders to projects.
3. Review the **Suggested** tab. Each suggestion shows the folder and why it matches: **Project number** or **Name**. Select **Accept** or **Reject** for each one, or select **Accept all suggested**.
4. To link a project without a suggestion, open **Not linked**. In the project's row, search the folders in your projects folder by name, or select **Browse…**.
5. If the projects have past items, Cogram shows how many, with an estimate of how long they take. Select the checkbox to file them too.
6. Select **Link** with the number of projects.

Use **Linked** to check which projects already have a folder, and **All** to see every project.

### What good looks like

* Cogram says the projects are linked, and filing starts within seconds.
* The page shows the destination, your defaults, **Linked projects** with a status for each project, and **Recent filings**.
* Each filed item is in its type's folder inside the project's folder.

## Change how one project files

1. In **Linked projects**, open the project's **⋯** menu and select **Customize filing**. The project's **Overview → Settings** opens at its File export section.
2. Turn item types on or off, or change a type's folder. The project now shows **Custom**.
3. To go back to the firm's defaults, select **Reset to defaults**.

Project owners and leads can also link their own project here: select **Choose folder**, or **Use this folder** next to a suggested folder.

The project's **⋯** menu also has **Change folder**, **File now**, **File past items** and **Remove link**. Removing a link stops filing for that project. Files already filed stay where they are.

## Check what was filed

**Recent filings** lists the latest filed items, with the project and when each was filed.

* Select **Preview**, **Open in Egnyte** or **Open in Files** to see the filed copy.
* A failed item shows why it could not be filed. Select **Retry all failed** to file the failed items again.
* Select **View all** to see more.

To stop all filing for a while, select **Manage**, then **Pause filing**. Select **Resume filing** to continue. Nothing is filed while filing is paused.

## What Cogram files

Each type goes into its own subfolder inside the project's folder:

| Type            | What Cogram files                                                           |
| --------------- | --------------------------------------------------------------------------- |
| Meeting minutes | One Word file for each completed meeting                                    |
| Emails          | The original message for each email filed to the project, as an `.eml` file |
| Field reports   | One Word file for each completed field report                               |
| Photos          | Photos, next to the meetings and field reports they belong to               |
| RFIs            | One PDF cover sheet for each RFI that has an answer, with its files         |
| Submittals      | One PDF cover sheet for each submittal that has a response, with its files  |
| Transmittals    | One PDF cover sheet for each closed transmittal, with its files             |
| Documents       | Each document in the project's document register                            |
| Drawings        | The current revision of each drawing                                        |

Only emails your whole project team can see are filed. Emails restricted to certain people stay in Cogram.

## How fast items are filed

* Filing runs every few minutes. New items are filed within minutes of being completed. To file at once, select **File now**.
* **File server:** past items usually finish within a few hours.
* **Egnyte:** Cogram files up to about 700 items an hour for your firm, over 15,000 a day. A project's past items normally finish within a day. Cogram shows an estimate before you include them. When Egnyte's daily limit is reached, filing pauses and continues when Egnyte allows more calls. Nothing is lost. See [How much Cogram can do per day](https://docs.cogram.com/integrations/connecting-egnyte.md#how-much-cogram-can-do-per-day).

## Troubleshooting

#### Folder missing

A project shows **Folder missing**.

* **Likely cause:** The folder was moved, renamed or deleted, or Cogram lost access to it.
* **Fix:** Restore the folder or the access, or select **Change folder** and link the project to its new folder.

#### Daily Egnyte API limit used up

File export says "Paused: Egnyte's daily API limit is used up."

* **Likely cause:** The Service Account used all of its Egnyte calls for the day.
* **Fix:** Nothing to do. Cogram checks every few minutes and continues when Egnyte allows. Nothing is lost.

#### Field reports failed with no template

Field reports are counted as failed, with "no template".

* **Likely cause:** The report's type has no default export template, so Cogram cannot build the Word file.
* **Fix:** Set a default template for that report type.

#### Email is not in the folder

An email is in Cogram but not in the project's folder.

* **Likely cause:** The email is restricted to certain people, so it is not filed.
* **Fix:** This is expected. Only emails the whole project team can see are filed.

#### Earlier items are not in the folder

Items you completed before linking the project are not in the folder.

* **Likely cause:** The link files new items only.
* **Fix:** Include past items for that project. Each item is still filed only once.

## Next steps

* [Connecting Egnyte](https://docs.cogram.com/integrations/connecting-egnyte.md)
* [Connecting your file server](https://docs.cogram.com/integrations/connecting-your-file-server.md)
* [Your file server](https://docs.cogram.com/projects/file-server.md)


---

# 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.cogram.com/integrations/file-export.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.
