Dropbox: Why It's Workspace-Owner-Scoped

You hired a VA to help with file management. You both connected your own Dropbox accounts to the same AwardLettr workspace so each of you could see the case folders from your own desktop sync. A month in, you notice your folder structure is a mess. Some appraisals are filed under your Dropbox in "Smith, John - 12345". The same cases show up under the VA's Dropbox as "12345 - Smith, John". Sometimes the folder exists in one account and not the other. Nobody can tell which copy is the source of truth.

Without owner-scoped Dropbox, every sync was first-write-wins. Whoever happened to upload first that day decided where the folder lived and what it was named. Backfills made it worse. You ended up with two parallel Dropbox trees that drifted apart and could not be reconciled without manual cleanup.

This change matters most to any workspace with a VA, an assistant, or shared staff. Solo appraisers will not notice a difference because there was only ever one account in play. If you run your firm with help, this is the article that explains why the model changed and what you and your team should do now.

The real-world bug that drove this

Alyssa is a VA on Colby's workspace. Both of them had connected their own Dropbox account. When Alyssa uploaded a document, the sync used her Dropbox token. When Colby uploaded one, it used his. The result: a race condition on folder creation, inconsistent folder naming formats between the two accounts, and confusion about where any given case folder actually lived. Whoever wrote first won. The same case might have its folder in "Smith, John - 12345" in one Dropbox and "12345 - Smith, John" in the other, depending on which person hit Sync first.

First-write-wins is the wrong default for a shared resource

When two people share a workspace, they should be looking at the same files in the same folders with the same names. Per-user Dropbox tokens accidentally made that impossible.

The new model in one sentence

Every workspace has exactly one Dropbox account: the workspace owner's. Staff members, admins, and VAs all use that Dropbox indirectly through the workspace. There is no per-user override.

Old vs. new

Old: per-user Dropbox

VA and owner both connected separate Dropbox accounts
First-write-wins on folder creation
Inconsistent folder naming format between accounts
Two copies of the same case folder, one in each Dropbox
Nobody could tell which Dropbox was canonical

New: workspace-owner Dropbox

One Dropbox account per workspace (the owner's)
Consistent folders everywhere, every time
Owner sets the folder naming format, applies to all uploads
Staff and VAs can still upload through AwardLettr normally
No race conditions, no duplicate folders

If you are a VA who previously connected your own Dropbox

Your connection still exists in AwardLettr, but it is now bypassed for case-document sync. Documents are syncing to the workspace owner's Dropbox instead. Coordinate with the owner to make sure THEIR Dropbox is connected and pointed at the folder structure you both want. You can disconnect your personal Dropbox from the workspace if you no longer need it there.

How this compares to other integrations

Dropbox: workspace-owner-scoped

One account per workspace. The owner connects it once. Staff inherit access automatically through the workspace.

Email: per-user

Each user connects their own email account. Status updates and notifications go out as the user who triggered them. No change here.

Calendar: per-user

Each user connects their own Google or Microsoft calendar. Inspections sync to the calendar of whoever is the assigned appraiser. No change here.

What if the workspace owner has not connected Dropbox?

Then no Dropbox sync happens for that workspace, even if every staff member has personally connected Dropbox. The owner is the only one who can enable it. If you are a staff member or VA and you need Dropbox sync on, ask the owner to connect it from their account at /dashboard/settings/integrations.

Folder naming format is owner-controlled too

The owner picks the folder naming convention under Settings → Integrations → Dropbox (or Google Drive, or OneDrive). Staff and VAs cannot override this per-user; it is a workspace-level setting now.

Does this apply to Google Drive and OneDrive too?

Today, only Dropbox is strictly workspace-owner-scoped. Google Drive and OneDrive are still per-user technically, but in practice the workspace owner is almost always the one who connects them, and we recommend it that way for the same consistency reasons. If you are running into similar VA-vs-owner conflicts on Drive or OneDrive, the right move is for the owner to be the connected account.