Set audience targeting programmatically

someone pointed me to this blog but I still need further guidance:

I don't understand where to put the code snippet in the post.

also I don't understand what this means:
"We first take our web context and then take out the default.aspx web parts..."

Am I editing something in designer?
Who is Participating?
GreatGermConnect With a Mentor Commented:
That example would be with Visual Studio, but it may be more simple than that.

What version of SharePoint are you running?
What are you trying to change the audience targeting for (items, webparts, etc)?
sullisnyc44Author Commented:
moss 2007 wss 3.0

just trying to restrict acces to a particular view. someone suggested audience targeting and dvwp.

I have an attendance list that I need to restrict access to items (not always determined by the Author or Create By user)

I have filtered all of the views based on [Me]

but I need to mangers to be able to view All Items.
GreatGermConnect With a Mentor Commented:
Ah, unfortunately, audience targeting probably won't give you the end result that you are looking for since it really doesn't keep anybody from looking at the items if they want to and have a basic knowledge of SharePoint.  What you really need to do is use the permissions structure.  Thanks to great project ( you can actually just set this via a SharePoint Designer workflow.  

These are easy to setup and walk you through most of it.  The one thing you will need to decide on is how to determine who is permissioned.  It can be during the creation of the item (as a column) or via the workflow itself.
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

sullisnyc44Author Commented:
yeah  - the unfortunate thing about that project is that there is NO SUPPORT.

I believe (according to the discussions that there are issues when setting multiple permissions.

Have you used it? I need the following things to happen:
1. the authorizedBy people picker single field value needs to have permission to submit the item
2. the requestedby people picker single field value needs to have permission to edit and approve the item
3. a sharepoint group created on the site called 'Attendance Managers' needs to have access to the item (basically all items)

If you have set item permissions using to multiple values, including a group.
GreatGermConnect With a Mentor Commented:
I've used it quite a bit since it does simplify some common tasks and haven't run into any issues.

In response to your points:

1. Wouldn't this be the person that is creating the item in the first place?  If so, then the item already has the data of who created.
2. This would be where your would have the workflow change the permissions.
3. As long as the group has access at the list level then it will stay that way unless you take the permissions away at the item level.
sullisnyc44Author Commented:
nope - not always the creator

how should my permissions be set up then?

I have read access - all items (get an error about folders if I change it)
edit - only their own
sullisnyc44Author Commented:
how do I remove the default access to view by everyone?
remove access for visitors?
sullisnyc44Author Commented:
plus if I right click and look at Manage Permissions, nothing has changed.

on workflow step I added delete permission assignment for Home Visitors...

and everyone can still see everything
sullisnyc44Author Commented:
this is my workflow step
item permissions
GreatGermConnect With a Mentor Commented:
The permissions work by granting access. If a user or group isn't listed and granted access, the they won't be able to see anything. It sounds like you'll need two groups: one for the 'Attendance Managers' so they can see the items and one for the people that need to be create the items in the first place.

The workflow should be working fine as long as you are identifying the correct item in the list.
sullisnyc44Author Commented:
hmmm do you thing the issue is with 'Absences'? Is it somehow not grabbing the item id?
sullisnyc44Author Commented:
I just changed it from 'current item' to this on the Delete permission step...

 i think this is wrong :(
sullisnyc44Author Commented:
I think I finally have something (kind of) working!

I DID have to change the Requested By to Contributer and not reader but that makes sense. might also have something to do with because I was both the requester and manager name.

Maybe I will just write another workflow 'when the item has changed' if I don't want to let the user edit the the request again... that I will figure out.

I WAS getting this error on the workflow, but it IS changing permisions:
Status:   Failed on Start (retrying)  

but once I changed requested by to Contribute instead of reader it fixed this issue.

Absence Type: Pending Approval
Email Manager
removing attendance requesters
Grant Contribute Permission on Absences to Attendance Managers
Granted CONTRIBUTE permission to Manager:  domain\username
Granted CONTRIBUTE permission to Requester:  domain\username
workflow complete

I really can't thank you enough - this REALLY helped me out.
sullisnyc44Author Commented:
here is what the final step of my workflow looks like set item permissions
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.