Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Allow us to see all the folders a user has access to and easily remove them from member.
Currently you can see who are the shared people in a folder or file. We need to be able to select a person and see the folders and files they have access to, and then obviously un-share from there. Not being able to manage this easily is a significant security risk.
Google Sign-In and email aliases
I would like to report a usability issue related to Google Sign-In and email aliases, and propose an enhancement. I have: One Google account with multiple email aliases. One long-standing Dropbox account created with one of these aliases (let’s call it alias@domain.com), with its own Dropbox password. The same underlying Google account also has a “main” address (main@domain.com). What happens today: My Dropbox account email is set to alias@domain.com. If I try to log into Dropbox using “Continue with Google” and select my main@domain.com identity, Dropbox creates a completely new, empty Dropbox account for main@domain.com instead of linking the Google login to my existing Dropbox account. This behavior is consistent with the current requirement that the Google email must exactly match the Dropbox account email to use Google Sign-In. [help.dropbox](https://help.dropbox.com/account-access/google-sign-in) What I would like to achieve: Keep a single Dropbox account. Be able to: - log into that one Dropbox account with email + password (using alias@domain.com), and - also log in with Google Sign-In using the same underlying Google account (main@domain.com), without creating a separate Dropbox account. Feature request: If technically and security-wise feasible, I’d like to request: 1. A way to explicitly **link an existing Dropbox account** to a Google account for Sign-In, even if the Google address and the Dropbox email differ (for example main@domain.com ↔ alias@domain.com), possibly via a confirmation flow on both sides. [help.dropbox](https://help.dropbox.com/account-access/google-sign-in) Clearer safeguards to **prevent accidental creation of a new Dropbox account** when a user mistakenly uses Google Sign-In with an email that already corresponds (directly or via alias) to an existing Dropbox user. An advanced “login methods” section in account settings where a user can: - see which Google account is linked, - link/unlink a Google account, - continue to use email + password in parallel. This would greatly improve the experience for users with Google aliases or complex identity setups, and reduce accidental account duplication. Thank you for considering this request.
Manually disable folder shareability for sensitive information
So the use case is based on the desire of having sensitive information on Dropbox and eliminating the possibilty of accidentally sharing it with someone. The idea is for an option to manually turn off shareability of a folder. That way I dont accidentally create a link in a flurry and send our finances to a customer. There are other cloud services I could use that do this just for that information but who needs more passwords to remember.
Safeguard data on sudden drive-failure to avoid accidental deletions
The following issue cannot get solved by using any setting inside Dropbox or by external precautions – such as alerts on OS-level. Staff should find a support ticket on the problem I describe. A few months ago, we ran into a sudden mass deletion of all Dropbox data. It turned out that the reason was trivial – and that the same could happen again any day. An M2 SSD drive screwed into a Laptop didn’t sit perfectly tight in its slot and its pins had lost contact. This drive was used for Dropbox (local storage). Dropbox interpreted this loss of contact with the drive as full deletion and silently nuked all files we store on Dropbox (in Cloud + all attached machines). Technically, it's the same data loss you'll experience when you unplug an external drive with Dropbox running while the machine on. As we work with large files, we run Dropbox in a fashion that leaves all data on local machines and cloud-syncs it. Whenever a drive fails, it will therefore erase all Dropbox data. Rollbacks via Dropbox may help recover data. Yet, nothing can protect our Dropbox volume (hundreds of GB) from getting cleared in the first place. Any app or website that references data stored on Dropbox obviously would get affected by full data removal. This could cause substantial initial damage (blank pages, due to missing data) and likely lots of clean-up-work (once data got recovered). We already considered options to sniff out unexpected directory write operations – here's a Microsoft tool one may use on Windows. Such a tool, however, even when perfectly configured (shuts down local Dropbox when self-destruction is detected) would only rescue Dropbox data on local machines. Any 3rd party references to Dropbox data would still break – as they plug into Dropbox Cloud storage, which still gets nuked when a drive suddenly dies or disconnects. We would therefore like to see a mechanism for paid Dropbox tiers that kicks in, as soon as a computer logged into Dropbox issues the deletion of the full Dropbox volume. Dropbox should stop executing this command on its cloud instance and all drives machines it still can access and ask Admins (via E-Mail / Push Message), how it should proceed: A computer logged into this acount has requested to delete all files on Dropbox. The name of this machine is [“human-readable Computer Name”], Would you like to proceed? If yes, please enter your Dropbox Password. ⚠ This message may also get caused by a hardware error on the computer in question. As long as you do not confirm by entering your Dropbox password, no data will be deleted in the cloud or on connected computers. Enter password to delete all Dropbox data | Cancel delete operation Please consider this addition. It requires practically no GUI and would not introduce workflow changes. Yet, this little change would bring Dropbox data integrity to the next level.