Export and download files

Exporting content moves copies outside SynckHub’s permission, history, and audit context. Do it deliberately.

Choose the right export method

Method	Use it when
Download	You need a local copy of one or more files
Public shared link	External recipients need read-only access without a user account
Shared-link zip download	Recipients need a packaged copy of a shared folder subtree
SynckHub Desktop attach or local handoff	Your deployment supports desktop-assisted drag, clipboard, or local export workflows
Managed export or migration	You need offboarding, legal packaging, or large-scale export

Download files

1. Open the folder or focused view containing the file.
2. Select the exact file or files.
3. Choose Download or Export when available.
4. Confirm the scope.
5. Store or distribute the local copy according to your organization’s policy.

If the download action is unavailable, you may not have export permission for that scope.

Export a folder

Use folder export only when the recipient needs a package of content.

Before exporting:

• confirm the folder is the correct root
• check whether child folders contain sensitive content
• verify you have export rights
• consider whether a public shared link is safer than a static copy

Use public shared links for read-only distribution

Public shared links are often better than exports when recipients need temporary read-only access.

Use them when:

• the recipient should not become a repo member
• access should expire or be revoked later
• the source folder should remain the reference point
• the recipient may need zip download from the shared-link page

See Share and Manage Access for setup.

Use Desktop-assisted attach or handoff when available

Some deployments support desktop-assisted export flows for attaching, dragging, copying, or handing files to local applications.

Use those flows only when:

• SynckHub Desktop is installed and connected
• your organization supports the feature
• you understand whether the result is a local copy or a live SynckHub workflow

If the action is missing, use normal download or sharing workflows.

Export checklist

• Is this export necessary, or would in-platform sharing work?
• Is the selected folder or file scope correct?
• Do you have export permission?
• Does the recipient need edit access or only read access?
• Should access expire?
• Who is responsible for copies after export?

Common mistakes

Mistake	Better approach
Exporting active work repeatedly	Use shared access or a public shared link
Downloading sensitive folders casually	Confirm policy and scope first
Sending path links to external recipients	Use guest access or public shared links
Assuming downloaded files stay governed	Treat exported copies as outside SynckHub control

Next step

Continue to Keep Apps Updated.