Among the many benefits that come with using Facebook developers is the option to draft a custom Authorization Dialogue, giving administrators a hand in how their custom app's users are notified about their permission choices. This dialogue comes into play when a user faces a prompt asking that they allow third party application access to their promotion and, as such, should stress the benefits and security to be had in connecting with the third party application.

To create a custom Authorization Dialogue, navigate to Facebook.com/developers,  select the pertinent custom application, and under advanced settings, enable "Enhanced Authorization Dialogue".

Next, select "Auth Dialogue" under "Settings".  

A number of text fields allow you to construct the message users will read. 

When customizing your Auth Dialog, you will be asked to provide the following information. The first four text fields are especially important  in helping users determine whether or not to add your app, while the remainder are not mandatory. 

1. Logo: Upload a logo for your app

2. Headline: A one line description of your app

3. Description: Longer description of your app which will be shown as subtext, under the Headline.

4. Privacy Policy URL: Your privacy URL

5. Terms of Service URL: Your terms of service URL

6. Add Data to Profile URL: Leave this alone

7. Explanation for Permissions: If your app requires extended permissions other than email and publish_actions, a second Auth dialog screen will appear after the user authorizes the initial Auth Dialog. This is the text explaining why you need additional permissions. More than the first authorization dialogue, this should acknowledge information is being collected, and for responsible reasons. 

8. Default Activity Privacy: This field sets the Auth Dialog with a default action visibility setting which users can update when they authorize your app. By default, this value is set to NONE, which means your actions published will follow the user's default privacy permissions. A user's default privacy permissions is set by the user whenever he or she posts on Facebook. If they  change it to friends only, the permission will be updated to friends only. If they change that to public, your app activity will turn into public actions. **Possible settings: None, Friends, Me only, or Public. The user can change the Activity Privacy on the Auth Dialog.

AUTHORIZATION DIALOGUE BEST PRACTICES - What to do, and what not to do:

DO

-be concise

-communicate the benefit of allowing the application to access profile information

-be exciting and reiterate what users can win by participating 

-assume a user perspective - This individual has demonstrated interest in the promotion, and the authorization dialogue should be seen as a way to corroborate their interest, not make them reconsider

DON'T

-be wordy or uneconomical with text

-use too many "threatening words" like permissions, grant, allow us, give information, share information, privacy or account details.

- resist the temptation to explain why permissions must be extended by the user for the application's functioning or to promise no misuse of information. What is intended as transparency may actually confuse an entrant more and leave them disbelieving.  

AN EXAMPLE OF WHAT TO AVOID (note: Test Application is the custom app's name in Facebook Developers. If you'd like to change the title, change the app name.) 

GOOD EXAMPLES: