We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Change file permission, files.content.read
Dear support,
Currently, my app is using the "long lived token" to access to the app folders. The permission for that folder was set to "files.content.write". I would like to add the permission, "files.content.read". I was able to make that change in the app console. The box next to it is checked to indicate the change is made. However, when trying to download a file in my app, I was rejected by this "files.content.read" permission. Can I change the permission without needing to re-generate the access token? I do not want to lose my existing long lived token since the app is distributed around 100 spots.
Thanks!
It is not possible to increase the permissions (e.g., add another scope) on an existing access token or refresh token. Adding a scope to your app via the App Console does not retroactively grant that scope to existing access tokens or refresh tokens.
That being the case, to make any API calls that require that scope, you'll need to re-authorize the app to get a new access token (and refresh token, if being used) with that scope.
Refer to the OAuth Guide and authorization documentation for more information.
- Greg-DB
Dropbox Staff
It is not possible to increase the permissions (e.g., add another scope) on an existing access token or refresh token. Adding a scope to your app via the App Console does not retroactively grant that scope to existing access tokens or refresh tokens.
That being the case, to make any API calls that require that scope, you'll need to re-authorize the app to get a new access token (and refresh token, if being used) with that scope.
Refer to the OAuth Guide and authorization documentation for more information.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
