Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Monday, September 10, 2012 9:05 PM
I have created a list programmatically.
I do not want the users to add new columns or views to the list but they should be able to add or delete items .
Are there any list properties which can be used or what would be the best way to go about it.
Appreciate any suggestions.
Tuesday, September 11, 2012 3:20 PM ✅Answered
Yes, you'd break permission inheritance on the list, from whatever site it is pulling its permissions from. Then, give the appropriate group/user Contribute or whatever combo of custom permissions desired.
Monday, September 10, 2012 9:50 PM
If you give users "Contribute" on the list, they can add and delete items, and only customize their own personal views, not public views. They won't have access to change public views or modify columns--for that, they'd need the manage lists permission. For more info, see here:
http://technet.microsoft.com/en-us/library/cc721640.aspx
Tuesday, September 11, 2012 5:44 AM
Hi,
Donia Strand is right. When you give either Designer or Full Control Access to the user they would be eligible to edit properties of the list so what you need to do is to just limit their permission up to the Contribute access or you might just want to create another permission levels that would only allow user to just edit/add/delete items and nothing more :)
Let me know if this helps, Ranjoe
Tuesday, September 11, 2012 3:18 PM
Thanks for the replies.
Will this solution be viable ?
1. Remove all the permissions levels after the list is created programmatically.
2.Add the permission level that would allow the user to add/edit/delete items.
So that when the user accesses the list through a webpart he won't be able to manipulate the list settings.
Tuesday, September 11, 2012 3:24 PM
Great . Thanks a lot for your help, I was racking my brains a lot over this one.