When applying for production, we'll review that your app doesn't request an unnecessarily broad permission based on the functionality provided by the app. Your app should use the least privileged permission it can. You get full access to all the files and folders in a user's Dropbox. Your app gets read and write access to this folder only and users can provide content to your app by moving files into this folder. App folderĪ dedicated folder named after your app is created within the Apps folder of a user's Dropbox. Selecting App folder will grant you scoped access only to your app's dedicated folder while selecting Full Dropbox will grant you scoped access to the user's entire Dropbox. The selected scopes control an app's behaviors and actions while the access level controls the content and resources the app can act on.

When creating a scoped app, developers need to select the level of content access. If you're migrating from a legacy app, we recommend reading Migrating App Permissions and Access Tokens. You can learn more about scopes in the OAuth Guide. During the OAuth flow, a user authorizes the app to have that specific level of access. Scopes are selected in the Permissions tab of an app's settings page. The DBX Platform uses scopes so developers can specify the level of access that their app has to user and team Dropbox data.

Your app's permissions control which data your app can access in a user's Dropbox.

As part of the process, you'll need to choose the right permission for your app. When you start building an app on the DBX Platform, you'll need to create a Dropbox app in the App Console. Be sure to also refer to the developer branding guidelines and terms and conditions as you design your app. This is your goto reference for building great apps on the DBX Platform and sailing through the app review process.

Dropbox developer documentation