I'm reading up on Sharepoint and it's security limitations in terms of unique permissions on items within lists (max 2000 per level).
I will have a list/doclib with about ~800 entries, probably with unique permissions set - no problem here.
But I also want to create a "to-do" task-based list per entry. That means I might have 5 tasks per entry in a separate task list - 4000 items with unique permissions might become a performance problem.
Basically I want the tasks to be editable by the assignee (the one who the task was assigned to) as well as certain groups (Administrators). Others should not be able to edit/view the task. I'm wondering what you would propose as the best way to handle this.
It would be no problem setting permissions for the task list itself, so only certain groups can view/edit; the problem is that someone totally different (in a non-admin group) also needs to work on his/her tasks (but not on any others) - the only way I see is using unique permissions per task or to group tasks into user- or group-based folders / lists.
Any other way I am missing?
Can Sharepoint 2010s new method SPRoleAssignmentCollection.AddToCurrentScopeOnly help me?