> For the complete documentation index, see [llms.txt](https://mozarkdocs.gitbook.io/appx_documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mozarkdocs.gitbook.io/appx_documentation/test-infrastructure-documentation/file-management/overview.md).
# Overview
## File Management
Use this page to upload, organize, and share app builds, test data, and other artifacts used in testing.
### Accessing File Management
Navigate to **File Management** in the sidebar.
Files are scoped to the currently selected organization, app, and project.
Confirm that your working context is correct before uploading.
### Uploading a file
1. Click **Upload File** at the top-right of the page.
2. In the upload dialog, click **Choose File** or drag a file into the upload area.
3. Optionally, add metadata as key-value pairs.
4. Click **Upload**.
Use metadata to capture context such as version, environment, or test suite association.
Examples:
* `version: 2.4.1`
* `environment: staging`
* `suite: smoke-tests`
For large files, the portal shows upload progress.
Some file types require a short server-side processing step.
This appears as a **Re-signing** status and usually completes within a few minutes.
{% hint style="warning" %}
Do not close the upload dialog while a file is uploading.
Closing the dialog cancels the transfer.
If re-signing continues after the dialog closes, the portal keeps polling for status updates in the background for up to five minutes and refreshes the list automatically.
{% endhint %}
### File table columns
| Column | Description |
| --------------- | -------------------------------------------------------- |
| **Name** | Original filename as uploaded. |
| **Path** | Storage path inside Mozark's file store. |
| **Status** | Current file state, such as `Available` or `Re-signing`. |
| **Size** | File size in KB, MB, or GB. |
| **Uploaded** | Timestamp when the file was uploaded. |
| **Uploaded By** | Email of the team member who uploaded the file. |
| **Actions** | Download and delete actions. |
### Viewing file details
Click any file row to open the File Detail Panel.
The panel slides in from the right side of the screen.
It shows full file information, including metadata, MIME type, and a download button.
You can also edit metadata from this panel without re-uploading the file.
### Downloading a file
Download a file in either of these ways:
* Click the download icon in the **Actions** column
* Click **Download** in the File Detail Panel
The file is fetched securely and saved to your browser's default download location.
### Deleting a file
Delete a file in either of these ways:
* Click the delete icon in the **Actions** column
* Click **Delete** in the File Detail Panel
The portal asks for confirmation before deleting the file.
Click **Delete** to confirm or **Cancel** to keep the file.
{% hint style="warning" %}
Deletion is permanent.
There is no recycle bin or undo.
If an Appium test suite references a deleted file in its capabilities, those runs will fail.
Coordinate with your team before deleting shared builds.
{% endhint %}
### Column visibility
Click **Columns** at the top-right of the table to show or hide columns.
This works the same way as the Sessions view.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://mozarkdocs.gitbook.io/appx_documentation/test-infrastructure-documentation/file-management/overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.