Skip to content

Collaboration - File sharing — introduction

This page introduces the accsyn File Sharing subsystem — available on Cloud or on-premises (BYOS) storage, and integrated with the Media Vault.

The core idea: share specific subfolders of a project tree on production storage — not the whole volume — so external users and partners can work inside production safely. Access is controlled with ACLs; transfers use the secure, accelerated ASC protocol via the Desktop App.

Get started

We recommend this short video introducing file sharing:

Tutorial

Set up file sharing step by step with this tutorial:

FTP server replacement

What is accsyn File Sharing?

In short, it is an FTP replacement: strong ACL-based access control combined with fast, secure, resumable transfers over ASC — without exposing broad production disks to partners.

Why file sharing?

Film and media production move large file sets between studios, vendors, and remote teams. Operators need precise control over who sees which folder, with audit trails when access must be reviewed later.

accsyn is built for that: share only the project subfolders partners need (for example FROM_VENDORS/acme beneath a larger project tree), keep the rest of production storage private, and still give them a seamless download/upload experience over ASC.

How does file sharing work with accsyn?

The simplest one-shot transfer is a delivery — a time-limited package. File sharing is for ongoing access: permanent (or long-lived) folders, homes, and collections on your storage.

Terms used throughout this guide:

  • ACL — Access Control List; defines which employees may access volumes, and which standard users may access shared folders (or specific subpaths beneath them).
  • Share — Internal accsyn entity for a container of sharable files and folders: a volume, shared folder, collection, or home. The share API code must be unique within the workspace. In the API, paths often use share=<ident>/… notation.
  • Volume — Root folder exposed to accsyn on a file server. accsyn cannot reach files outside this root. All sharing, delivery, and title management happens inside volumes. BYOS workspaces may define many volumes. Administrators have full volume access; employees only to volumes they are granted; standard users never get direct volume access.
  • Shared folder — A folder beneath a volume (or the volume root) shared with standard users through ACLs. You can grant access to the whole share or only a subfolder — ideal for integrating vendors into one project area without opening the rest of the tree.
  • Collection — A virtual folder of files and folders gathered from one or more volumes, shared like a shared folder.
  • Home — A per-user shared folder (named after the user email) for upload/download outside the main production area. Off by default; enable in Settings.

Access by role:

  • Administrators — Full access to all volumes. Invite admins carefully.
  • Employees — Access to volumes granted by administrators; can create shares, deliveries, and audit activity.
  • Standard users — Apart from deliveries sent to them, only shared folders, homes, and collections they are granted via ACL.

Can I share titles and media in the vault?

Yes. The title library sits on a normal folder structure on storage, so you can share folders and create collections as with any other content.

A common pattern is a permanent DCP collection shared with selected users.

Can I share files on my own local or cloud storage?

Yes. With BYOS you install on-premises or cloud servers so file sharing and delivery run against your own storage.

Can my clients share folders on their local machine?

Yes. This is local file sharing: a user maps a shared folder (or volume path) to a folder on their computer and grants workspace operators read and/or write on that mapping.

While their client is online, elevated users (administrators and employees) can:

  • Pull — with read access, upload from the mapped folder onto main storage or a site.
  • Push — with write access, download from main storage or a site onto the mapped folder.

Typical uses: working from home, or vendors keeping a local work area that mirrors production folder structure. Transfers use ASC when the Desktop App or User server is the endpoint.

Configure mappings in the Desktop App (app running and user signed in). For 24/7 access without a logged-in desktop session, install a User server (accsyn daemon/service). See Hosts.

Can I share files and folders on a remote office or cloud site?

Yes. In a BYOS (or Enterprise) workspace you define sites — remote offices or cloud locations — usually with one or more site servers. Assign servers and elevated clients so accsyn knows where they are.

Site servers sync material between HQ and the remote site, serve shared storage there, and can take over transfers initiated by clients on that site so jobs continue when individual Desktop Apps close.

See Site administration and the Remote office sync tutorial.

Next: Work with accsyn File Sharing