Drive Sync: Pick the Right App for Your Setup

You don't have to live inside a browser tab to use TrekMail Drive. Drive Sync lets your Mac, PC, or phone see your Drive as if it were a folder on the device, so files appear in Finder next to your Documents, in Windows Explorer next to "This PC", or as a place to upload from your phone's Photos.

This page is the short tour: what Drive Sync is, which app to pick for what, and what each connection costs in terms of speed and reliability.

How it works at a glance

TrekMail exposes Drive over WebDAV, a standard file-sharing protocol. Use a WebDAV-capable client on your device, copy the Drive URL supplied by TrekMail, and sign in with a device password. The client then lets you browse and work with the files within its own interface.

Every connection uses two things:

• Your Drive URL: copy the URL shown for the device scope on the Sync devices page.
• A device password: one per app or computer, generated on the same page. You can revoke any one of them without touching the rest.

Once that's done, you can drag, drop, edit, and save like any local folder. The sync client handles uploads and downloads behind the scenes.

Two places to issue a password

You can generate device passwords from either the dashboard or webmail, depending on who you are:

• Dashboard (/drive/devices), account owners and admins. Lets you issue both account-wide passwords (the default, see everything) and mailbox-scoped ones (locked to a specific mailbox). Shows the complete inventory across the whole account, including rows that mailbox users created from webmail (each row carries a small badge, 🖥 "Created via dashboard" or ✉️ "Created via webmail (name@example.com)", so you know which surface produced it).
• Webmail (inside the Drive view → Sync devices button), any mailbox user, even ones without dashboard access. Always scoped to their own mailbox, only mailbox-level permissions offered. Same one-time password reveal, same revoke flow.

Account owners can revoke any password regardless of which surface created it. Mailbox users only see their own.

Which app should I use?

Six clients, two surfaces (account-wide vs per-mailbox), and a handful of trade-offs. Here's a quick decision tree:

On a Mac

• Just want files in the Finder sidebar? Use macOS Finder. It is built in and is useful for everyday browsing and manual file work.
• Uploading big videos, archives, or hundreds of files at once? Use Cyberduck. It gives you a dedicated transfer interface and is a good option when you want to watch or retry transfers.
• Backing up automatically every night? Use rclone with a cron job. Command-line; the most reliable option for unattended jobs.

On Windows

• Just want a drive letter (Z: → your Drive)? Use Windows Explorer. It is built into Windows.
• Big files or lots of them? Use Cyberduck, the same app as on Mac, with a dedicated transfer interface.
• Backups and scripted moves? Use rclone, runs in PowerShell or Task Scheduler.

On Linux

Linux Explorer-equivalents (Nautilus, Dolphin) all speak WebDAV out of the box. They connect the same way Windows or Mac do. For headless work or automation, use rclone.

On Android

Use a WebDAV-capable Android app and follow the Android setup guide. Keep the device password in the app that uses it, and give it only the permissions that app needs.

On iPhone or iPad

Use Documents by Readdle or another WebDAV-capable iOS app. Follow the app-specific guide and test with one small file before relying on it for a large transfer.

What each connection can and can't do

A short comparison so you know what you're choosing:

"Auto-sync" means the files always look in-sync without you doing anything. The browser-managed apps (Finder, Explorer, Cyberduck, file managers on mobile) load and save on demand, files only travel when you open or modify one. rclone is the only option that can run on a schedule and keep a local folder mirrored.

Account-wide vs mailbox-only access

Every device password can either:

1. See Account Drive: files in the Account Drive surface and folders shared with the account. This does not expose each mailbox's private Drive.
2. See only one mailbox's personal Drive (plus any shared folders). Use this when you're handing the password to someone who shouldn't see the rest of the account: an employee on their phone, a contractor on a temporary laptop, an automation that only handles one inbox's files.

You pick this on the Sync devices page when you create the password. The mailbox-scoped option is the Advanced section in the form, collapsed by default, so the simple "all my files" case stays one click.

Mailbox-scoped passwords use a slightly different URL: https://YOUR-DOMAIN/dav/files/mailbox-N/ instead of /dav/files/account/. The dashboard shows the right URL after you generate the password.

A typical first connection

For a safe first connection:

1. Open Sync devices in the dashboard.
2. Click "+ Add new device". Name it something you'll recognise, "MacBook, Finder", "Backup script", "Work iPhone".
3. Choose only the permissions the app needs, select an expiry that fits the device, and click Generate password. Copy the dsync_… string into your password manager.
4. Open the platform guide that matches your app (links above). Each one is a short copy-paste setup using the same Drive URL and the password you just created.
5. Test with one file, drag it in or out, to confirm the connection works.

That's it. From now on, your Drive is just another folder.

What's next

• Sync devices page reference, the dashboard UI, every checkbox explained.
• The seven platform setup guides linked above, pick one to follow next.
• Drive Sync Troubleshooting, what to try when a connection doesn't work.
• For developers integrating Drive Sync alongside the API or MCP server, Drive Sync Architecture covers the URL layout, scope model, and audit-log story.