# Organisation files
Source: https://docs.aden.space/docs/help/work-together/organisation-files

A shared drive for the organisation itself. Upload, foldering, rename, bulk download and share links for any file the org keeps, alongside its writer contracts.
{/* Generated by `bun docs:publish` from docs/features/organisation-files.md: edit the spec, not this file. */}

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

Teams already have a **Documents** page. Organisations now have the same thing
for themselves: a drive at **Workspace › Files** that holds everything the
organisation keeps but that doesn't belong to any single artist team. Brand
assets, templates, insurance papers, rider PDFs, decks, exports.

It is meant to replace the generic cloud drive an organisation would otherwise
run alongside Aden. It is the **same drive as the team one**: the same upload
box, the same folder tree, the same file types (documents, spreadsheets,
archives, images and video) and the same plan-based upload limit.

## Using it [#using-it]

**Upload.** Drag files onto the drop zone, or pick them from a connected cloud
provider (Dropbox, Google Drive, OneDrive) if one is linked.

**Folders.** Folders are created by uploading into them. Open a folder and use
**Upload here**, and the file is filed under that path. Renaming a folder moves
everything inside it.

**Rename, download, delete.** The three-dot menu on any file renames it,
downloads it, copies a link, or deletes it. Select several files to download
them as a ZIP or delete them together.

**Comments.** Each file has its own comment thread, so feedback stays attached
to the file instead of living in chat.

**Contracts are read-only here.** Contracts raised against a writer are filed
against the organisation too, so they appear in a `Contracts/` folder. They can
be read and downloaded from the drive but only edited or voided on the
**Contracts** page: the drive never lets someone delete a signed agreement.

## Who can do what [#who-can-do-what]

Anyone who is a current member of the organisation, or of a parent
organisation: can open the drive and download from it. Changing files (upload,
rename, delete) needs a staff-side role: owner, admin, manager, member or
staff. Members carrying the `artist` or `viewer` role see the drive read-only
and are told why rather than having the controls hidden.