SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It only takes a minute to sign up.
Sign up to join this community
I have a main list, which I distribute on different pages. The idea is that different departments will fill in their tasks and only be able to read/write information associated with their department.
The only solution I have is to control this through views. But I do not know if this is a good solution. It is important that users do not access other departmental tasks.
If you strictly want to go with one main list, you'd need to handle this with views and preferably using audience targeting. A similar question can be found here. However, if you will handle the requirement like this, users still have the same permission to items which wouldn't be shown in the view targeted to them - the items just wouldn't be directly visible, although quite trivially accessible with some understanding of SP.
Another (likely bad) option would be to handle list items each with unique permissions, but this would be a terrible solution from managing point of view.
Generally I'd suggest to handle this requirement by creating several lists. Possible usage of lookup fields and/or content queries for simulating "a main list" could be implemented on top of that.
As @moe said one possible solution is to manually assign permissions to items.
To automate this process via a SharePoint designer workflow:
Add groups with department names.
Against each item, create a column which stores which department this item is meant for.
Then adding a step in workflow to first remove all permissions and then assign permission to the group name stored in the column of the item.
This way you will not have to use views. Whether the user opens "All items" view or opens the list itself, he will be able to see only the items assigned to his department.
