What are Scopes?
You may see a few notes referring to "scopes" in the AE Dashboard and on social apps. Scopes are basically a service's custom API permissions - each scope refers to a specific permission regarding what information you have access to on the service's API.
For example, Spotify uses scopes to give permissions to various aspects of their user's information, such as their library, things they have recently listened to, their playlists and so on. Each of these elements has a corresponding scope that your Spotify application needs to get permission from the user to give you access to.
The user will see your request for permissions - each line below referencing a specific Spotify scope - when registering using your application through the Appreciation Engine:
The Appreciation Engine handles these scopes by automatically assigning all of the scopes required by that service to perform our social tracking. These are referred to in the dashboard as "default scopes" and you can see them by opening the service popup for an individual service in your dashboard application:
Advanced Scope Changes
You can override any of these default scopes using the form in the popup above. For example, your application may only be interested in gathering users' Spotify Playlist data, in which case you could just specify the playlist scopes. This would be reflected in the permissions the user sees when signing up.
Note: when you override the default scopes, only the scopes you have specified will be granted. In the example given in the previous paragraph, you would no longer have access to your user's library data etc.