Case study
How Dropbox moved integrations to narrower permissions
Dropbox's OAuth migration gave existing apps compatible defaults and gave their maintainers a way to identify the permissions each feature used.
A platform change for existing apps
In September 2020, Dropbox published a migration guide following the introduction of scoped apps and short-lived access tokens. Existing integrations had been created under broader access types. When maintainers opened the permissions screen, Dropbox preselected scopes corresponding to the app's legacy type. This gave developers a working starting point for the transition.
Getting from a default to a precise request
Dropbox advised maintainers to list every API endpoint used and match each one to the permission in its reference documentation. The guide illustrated the difference between listing a folder's contents and downloading a file. One operation needs permission to read metadata, the other to read file content. It also distinguished interactive use from background work, which can require a refresh token to continue after an access token expires.
A lesson for an integration handover
Give a maintainer a table with one row per user-visible feature. For a nightly export, record the API operations it calls, the permissions those operations require and what happens when access expires. Compare that table to the permissions shown during connection. It gives reviewers a concrete way to spot an unused capability and gives support a place to look when one specific feature starts failing.