I am having some problems locking down the library lists available to my developers. I'm sure previously, if they attempted to change their library list, using the synon library lists previously setup, and they were not authorised to one of the libraries in that list, it would fail. For some reason it doesn't fail now and we get swamped with authority errors because they have "live" objects in a developers job library list.
I have looked at the lists themselves and there doesn't seem to be a way of securing them from there. There has been no authority changes to the libraries themselves and I have been through and checked them.
Any help greatly appreciated!
May 13, 2009 11:12 AM
May 15, 2009 4:35 PM