> For the complete documentation index, see [llms.txt](https://docs.fenixpyre.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fenixpyre.com/fenixpyre-for-users/cmmc/how-to-upload-files.md).

# How to upload files

## CMMC Share Links - Multipart Upload Guide

### Overview

CMMC share links now accept uploads directly from FenixShare. Every transfer uses a hardened multipart pipeline built just for CMMC, so even large or sensitive files arrive intact without requiring the Windows agent.

### Who Can Upload

* Folder-based CMMC share links where you already hold edit rights.
* Primary users plus any invited collaborators who have been granted edit permission.
* Upload remains **multipart-only for CMMC** to meet the connector’s reliability and compliance requirements.

### How to Upload

1. Open the CMMC share link and choose `Upload`.
2. Select one or more files. FenixShare automatically slices them into encrypted chunks.
3. Track progress in the refreshed upload panel:
   * Real-time percentage for each part.
   * Clearly labeled states (Preparing → Uploading → Encrypting).
   * Inline error messaging if a chunk stalls.
4. When the upload completes, the file list refreshes.

### Why Multipart Matters

* Handles large transfers without timing out typical single-request limits.
* Recovers gracefully from unstable networks by retrying only failed parts.
* Validates every chunk before sealing the encrypted object in the CMMC vault.


---

# 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.fenixpyre.com/fenixpyre-for-users/cmmc/how-to-upload-files.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.