Keep Facebook App
Like everything else we create in the social media space…
There is often certain content that is either inappropriate for a broader audience or simply better for a more specific audience.
An example of this might be the dozens and dozens of photos you might shoot on your smartphone and upload to a photo app from a enjoyable business conference you are attending this upcoming weekend.
Now, while one or two of these photos might be no big deal to your family and school friends… fifty of them flooding the stream is likely to be another story!
So what to do?
We’ve talked in a prior post about how to use Facebook (custom) Lists to control post privacy… and hopefully you’re already taking good advantage of lists.
Unfortunately, unless we tell them otherwise, applications that can publish to Facebook will use the default post setting… which generally speaking is the last privacy setting we published with manually.
So… if I made a public post, on my profile, so that my subscribers could see it… and then I installed Instagram on my phone and sent a photo from Instagram to Facebook… the resulting post would be public with very little ability to change that “on the go”.
I ran into this recently when I was trying to get Cardio Trainer to publish from my phone… to my wall.. but not quite to everyone!
In most mobile apps, you’ll find that you can’t configure the default post visibility, from your phone. (Working from a desktop/laptop is different as the authentication dialog box usually offers you that option.)
Fortunately, if you’re near a PC any time BEFORE you need to let the app do its magic… the setting is easy to adjust.
In fact, you could even set it to one setting “just for this conference” and then adjust it back to its usual setting after the business stuff is finished.
How To Set and Control The Visibility
of an App’s Auto Postings On Facebook
(click on the image for a closer look)Step 1: In your upper right-hand menu, on the far right edge, you will see a small white down-arrow. Click this and then select “Settings“. (This was formerly titled Account Settings)
Step 2: In account settings, use the left-hand navigation menu to select “Apps” (app settings)
Step 3: Scroll through the apps you have approved (remove any you won’t need within the next 30 days to reduce hacking troubles) and then find the app that we need just adjust. (You will likely need to click “Show All” to see the full list.)
Step 4: To the right of the app name, when you hover your mouse over the app name, will be a pencil icon that says “Edit Settings” (click it). This opens the permission settings for that app.
Step 5: Find “App Visibility and Post Audience” … and to the right of that, open up the permission drop-down box. (By default this may say: Friends, Friends of Friends, or Public unless you customized your default post settings).
Step 6: Select “Custom” in the dropdown, and in the “Custom Privacy” box you can explicitly show it (only) to certain people (or lists!) and you can hide it from certain people (or lists!). Hide overrides visibility so is used to refine visibility.
For example: Show it to all of my co-workers who are in list name “CoWorkers”…. but, hide it from Mr. Boss Man.
Another example: Let’s say we’re planning a party for a family friend….. Show it to all of my “Family” list… but, hide it from “Becky” (the birthday girl).
Have a small group conversation: Show the post only to Dan, Stacey, Beckie and Cathy
Click “Save Changes” and you’re done!
There are lots of ways to take advantage of customizing your post visibility settings – even for remote app postings as we see here.
Once set, the apps will not automatically grab your more recent post privacy setting and risk stuff “doing its own thing”!
When combined with controlling post privacy and good use of Facebook custom lists, you have excellent control over “who sees what” as long as it’s written on your own timeline wall.
Share this post with your friends, family and colleagues… they will thank you!
~ Kim ~
Simple Tech Tips For Marketing
Post originally published October 5th, 2012 and updated for changes on October 9th, 2015