> For the complete documentation index, see [llms.txt](https://docs.scaleflex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scaleflex.com/digital-asset-management-dam/library/airbox.md).

# Airbox

Third-party asset upload

Airbox enables non-registered users to upload files through public links, offering a simple way to collect files. You can set optional activation and expiration dates and password protection for each Airbox instance. Additionally, you can invite users via email, set upload limitations, and receive notifications when assets are uploaded.

Use Airboxes to:

* Collect files from external partners
* Receive campaign assets from agencies
* Gather user-generated content

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FnDSMFEPV5MIjQMnnYGpO%2FScreenshot%202026-04-27%20at%2013.33.20.png?alt=media&amp;token=a9a3e49b-f96d-4a63-a071-89ef473a29fe" alt=""><figcaption></figcaption></figure>

## Creating an Airbox

To create an Airbox instance:

* Select **Airbox** from the left menu in your Scaleflex DAM library.
* Click on + Add airbox.
* Enter a meaningful title and description for the new Airbox.
* Select the target folder in Scaleflex DAM where uploaded files will be stored. If the selected folder is already in use by another active Airbox, an alert will notify you. Choose a unique folder to avoid conflicts.

Optional settings:

* Set start and expiration dates.
* Enable password protection.
* Set limitations per file size, total number of uploaded assets, etc.
* Choose who will receive notifications when files are uploaded to the Airbox, when they are sent and how they are delivered. See [Airbox notifications](/digital-asset-management-dam/library/airbox.md#airbox-notifications).
* Set which file metadata fields to be filled in on upload.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2F4h7gQJie8Hfc18ojKdns%2FScreenshot%202026-04-27%20at%2012.18.45.png?alt=media&amp;token=019c04fd-ae87-4619-8a8f-d6aa216d908f" alt=""><figcaption></figcaption></figure>

## Airbox notifications

Airbox notifications let you know when files are uploaded to an Airbox. You set them up in the **Settings** step when you create an Airbox, and you can change them at any time by editing the Airbox.

To turn notifications on, enable **Set notifications**. The following defaults are applied, and you can change any of them before saving:

| Setting                | Default             |
| ---------------------- | ------------------- |
| Recipients             | Airbox owner        |
| Notifications schedule | When uploads finish |
| Notify via             | In-app              |

<div align="center"><figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2F9KOKW0qUvkeYzoYXQL0L%2FAirbox%20notification%20settings.png?alt=media&amp;token=eaa5a565-9287-4537-8ae4-84cb52174c81" alt="" width="563"><figcaption></figcaption></figure></div>

Turning **Set notifications** off clears the selected recipients and stops notifications for that Airbox.

### Recipients

Choose who receives the notifications. You can select any combination of:

* **Airbox owner**: the user who owns the Airbox.
* **Users**: one or more users from the project.
* **Teams**: one or more teams. Every member of a selected team is notified.

Users and teams who don't have access to the Airbox's target folder are listed but can't be selected.

When you click **Create Airbox** or **Save changes** with notifications turned on, the following rules apply:

* At least one recipient must be selected. If none is, the Airbox isn't saved and the message *Select at least one recipient to activate notifications.* is shown.
* If **Users** or **Teams** is ticked, it must contain at least one user or team. A ticked but empty option doesn't count as a recipient: add a user or team, or untick the option.

These checks run only when you save, so you can change recipients freely while editing. Each error message disappears as soon as you add a valid recipient.

### Notifications schedule

Choose when notifications are sent. Only one option can be selected.

* **When uploads finish** (default): you get one notification per upload session, whether it contains a single file or a large batch. The notification is sent once uploads to the Airbox have stopped for about 15 minutes, so a large upload followed by a few late files still results in a single notification. If uploads continue without a pause, you are notified at most once an hour.
* **Once a day**: you get one notification a day, sent at 6:00 UTC, covering the files uploaded to the Airbox since the previous one.

{% hint style="info" %}
Airboxes that had notifications enabled before **When uploads finish** was introduced keep the **Once a day** schedule. Edit the Airbox to switch to **When uploads finish**.
{% endhint %}

### Notify via

Choose how notifications are delivered. With **In-app**, notifications appear in the notifications panel of Scaleflex DAM. The channel is set per Airbox and applies to every recipient.

{% hint style="info" %}
Email notifications are coming soon. Until then, **In-app** is the only available channel.

This is separate from sharing an Airbox by email: you can already send the Airbox link to anyone by email from the Airbox list. See [Copy Airbox link and Share via Email](/digital-asset-management-dam/library/airbox.md#copy-airbox-link-and-share-via-email).
{% endhint %}

### Set up notifications through the API

You can also configure notifications when you create or update an Airbox with the [DAM API](https://dev.scaleflex.com/v5.html) (**Create Airbox** and **Update Airbox** endpoints). Notification settings go in `airbox_configurations.notifications`:

```json
"airbox_configurations": {
  "notifications": {
    "recipients": {
      "owner": true,
      "users": ["<user UUID>"],
      "teams": null
    },
    "schedule": {
      "daily": false,
      "on_upload": true
    },
    "channels": ["app"]
  }
}
```

| Field                | Description                                                                                      |
| -------------------- | ------------------------------------------------------------------------------------------------ |
| `recipients.owner`   | `true` to notify the Airbox owner.                                                               |
| `recipients.users`   | Array of user UUIDs to notify, or `null`.                                                        |
| `recipients.teams`   | Array of team UUIDs to notify, or `null`. Every member of each team is notified.                 |
| `schedule.on_upload` | `true` for **When uploads finish**.                                                              |
| `schedule.daily`     | `true` for **Once a day**.                                                                       |
| `channels`           | How notifications are delivered. Use `["app"]` for in-app. If omitted, notifications are in-app. |

The request is rejected with a `400` error (`ERR_BAD_INPUT`) when:

* A schedule is enabled but no recipient is set (`owner` is `false` and `users` and `teams` are empty): *You must specify at least one recipient to receive notifications.*
* Both `daily` and `on_upload` are `true`: *You can only enable one notification schedule at a time.*

To turn notifications off, set `owner` to `false`, `users` and `teams` to `null`, and both schedule flags to `false`.

## Uploading files via an Airbox

When a user opens the Airbox link, they would be able to upload files from their local device, via a URL link, to take a screen capture or to use the device camera.

{% hint style="info" %}
Airbox process flow:

Users open the link → upload files → optionally rename and add metadata → submit.
{% endhint %}

Users uploading through the same Airbox link cannot see each other’s files.

## Preview, Edit and Delete Airbox Instances

To Preview, Edit or Delete an Airbox, go to the '***Airbox***' section in the left menu of your Library.

Then select an Airbox item and click on the `...` menu.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FLn8AG0LR7A8bqko9mT9T%2FScreenshot%202026-04-27%20at%2012.45.50.png?alt=media&amp;token=d7adf06e-f050-4bfc-8e00-78a4ce685e66" alt=""><figcaption></figcaption></figure>

## Copy Airbox link and Share via Email

Hover over an Airbox to reveal options to copy its link or send it via email.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FjhBvmpH6MnmdLBv82TiT%2FScreenshot%202026-04-27%20at%2012.47.08.png?alt=media&amp;token=4a39da35-7205-4697-bc22-ed3bd620d5b7" alt=""><figcaption></figcaption></figure>

## Filtering options

You can filter only specific Airbox instances which match your business needs:

* Total - shows all existing Airboxes in the project
* Active - shows all currently active Airboxes where users can upload data. This category includes Airboxes without an expiration period and Airboxes whose expiration period is far away in the future.
* Protected - Airboxes with password-protected access
* Expiring - Airboxes that will expire soon
* Expired - shows Airboxes which can no longer be used for uploads (their validity is over)

## Airbox page Views

The airbox page supports two types of views, each dedicated to serving specific business needs.

### List view

This view orders the Airbox records in a table-like structure, having columns with details about the Airboxes. It is best for managing multiple Airboxes and comparing their details.

The user can choose sorting order and the level of detail of the shown information.

The **Name** column is always shown. You can show or hide the other columns:

| Column      | Shows                                             |
| ----------- | ------------------------------------------------- |
| Description | The Airbox description                            |
| Folder      | The target folder where uploaded files are stored |
| Status      | Active, Expiring or Expired                       |
| Validity    | The activation and expiration period              |
| Created     | The date the Airbox was created                   |
| Modified    | The date the Airbox was last changed              |
| Created by  | The user who created the Airbox                   |

Click the **Name**, **Validity**, **Created** or **Modified** column header to sort by that column. Click it again to reverse the order. By default, Airboxes are sorted by **Modified**, newest first.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FM2nTgPK8Xah9CUFFUUO4%2FScreenshot%202026-04-27%20at%2012.58.07.png?alt=media&amp;token=509f5f2c-c5b5-4442-9947-381041124031" alt=""><figcaption></figcaption></figure>

### Grid view

This view shows the Airbox instances as a grid of elements where the main focus is the individual Airbox. Best for quick visual browsing or filtering by creator.

In Grid view, you can sort Airboxes by **Name**, **Validity** or **Modified**.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FVTM1hOU3TlFHGADfBDj8%2FScreenshot%202026-04-27%20at%2013.05.39.png?alt=media&amp;token=f8999d63-ec40-491e-9979-324b6412364e" alt=""><figcaption></figcaption></figure>
