Tag Info

Hot answers tagged

4

No, audiences are not supported in the SharePoint client object model. Its only supported in the Server Object Model. In the past I created a Web Service in SharePoint that could take a user name and return the audiences for that user, leveraging the Server Object Model...but that approach probably doesn't work in your scenario.


1

Target audiences is primarily used for content roll-ups, it is NOT used for permissions or restrictions. Two quick options: 1) An onCreate SharePoint designer workflow that sets permissions to (a) user who created the item and (b) custom admin group you setup 2) In "Advanced Settings" under your Calendar settings, you can set "Read" permissions to "Read ...


1

AFAIK, Managed Metadata is not security trimmed or use Target Audience.. In this case you will need to write your custom Navigation Provider/Control.. Or use the Structural Navigation with Target Audience..


1

An audience just allows for promotion to those members, its not meant to be a security tool. For instance, you may put a web part on a page with an audience of Group1. So that when Group2 login in they don't see the WP but Group1 do. Think of it as a way to classfiy data and surface information to the correct user groups. Visibility of items is controlled ...


1

You can either place your links as hyperlinks in a Content Editor web part or you can use the Summary Links web part and place that web part on your page. Then "Edit Web part" >> Advanced >> Target Audience >> Add or Select your Group.


1

See my previous answer on the exact same issue here SP Group not for Navigation audience but there it is in the Browse! Yargh! It is a known bug with Target Audience not recognizing groups and can be fixed by providing unique names of SP groups per site collection.



Only top voted, non community-wiki answers of a minimum length are eligible