# Upload links
Source: https://docs.aden.space/docs/help/release/upload-links

Shareable links that let anyone send files into a team's documents, media, artwork or transfers, or into an organisation's drive, attributing the upload to the visitor's account when they're signed in to Aden.
{/* Generated by `bun docs:publish` from docs/features/upload-links.md: edit the spec, not this file. */}

## What it is [#what-it-is]

An upload link is a shareable web address that lets anyone, even people without
an Aden account: send files straight into your team. You create one from your
workspace, pick where the files should land (documents, media gallery, cover or
banner artwork, or as a received transfer), then share the link. Visitors open
it, drop their files, and the files appear in your team, tagged with whoever
sent them.

If a visitor is **already signed in to Aden**, the page shows who they're signed
in as and records the upload under their account, so the team can see exactly who
sent the files. Signing in only attributes the upload. It never adds the visitor
to the team.

## Using it [#using-it]

**Creating a link.** On Files, covers, media, banners, team documents or the
organisation drive, open the **Upload** chevron and choose **Request files**
(or **Request covers** / **Request banners**). The public links list only
shows once a link exists.

**Uploading files.** Open the link, choose your files, add an optional note, and
click **Upload**. You'll see a confirmation once they're sent. For event links you
can also opt to become a fan of the team.

**Who the files are from.** If you're not signed in, you can add your name and
email so the team knows who sent them (both optional). If you *are* signed in, the
form skips those fields and shows a "Signed in as `{you}`" note instead. The upload
is automatically recorded under your account. For event links you can also opt to
become a fan of the team.

**Where to go next.** Under the upload form, and again on the confirmation
screen once your files are sent. The page lists the artist's public pages that
actually have something on them (tracks, albums, mixes, events, tours, media,
posts, shop, songs and albums for sale). One tap takes you from "I shared my
photos" to the music and the next dates.

**A QR code to display at shows.** For a link attached to an event, the show's
**Media** tab carries a fan-footage card built around the code: the artist name
and avatar, the show name and date, a large QR that opens the drop page, the
artist's public page addresses, and the instruction to point a camera at it.
**Print poster** prints just that block. The rest of the workspace is left off
the paper, so it can go on the merch table; **Download QR code** saves the code
as a PNG for your own artwork, and **Copy link** copies the drop URL.

The card follows the show. Before the show it tells you to print the code or put
it on the venue screens; on the day it says fans can scan and send from the
floor; afterwards it shows how many files have come in and when collection
closes.

**A closing date.** Collection links for a show close relative to the show, not
to the day you made them, 1 day, 3 days, 1 week, 2 weeks (Pro) or 1 month (Pro)
after the show, or never. You pick it when you create the link, and the dialog
spells out the exact date it lands on. **Change closing date** on the card moves
it later at any time, including reopening a collection that has already closed
the printed code keeps working, so a poster that is still up in the venue is
never wasted.

**Requesting files into a folder.** In any file tree (track files, team
documents, the organisation drive) a folder's menu has **Request files here**,
and the **Add** tile inside an open folder has **Request files**. The link
created that way drops everything it receives straight into that folder instead
of a new one. The dialog says where the files will land.

**Requesting files into an organisation.** The organisation drive
(**Files** on an organisation) has **Request files** in the **Upload** chevron
when you can write. An organisation link is always drive-wide. There is no
track, album, event or gallery to point it at, and received files land in the
drive's folder named after the link. Read-only organisation roles see a
disabled **Request files** control with the reason.