Comments on: Beware of Cascading Deletes in WSS/MOSS http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/ Random musings Wed, 01 Feb 2012 17:28:56 +0000 hourly 1 http://wordpress.com/ By: Keith Richie http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-7690 Tue, 08 Mar 2011 14:48:55 +0000 http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-7690 Sudeep, dunno you could be right. It was a headache then, and a headache now. When I have time, I’ll update it for SharePoint Foundation and see if it still works the same.

]]> By: Sudeep http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-7689 Tue, 08 Mar 2011 14:35:33 +0000 http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-7689 Just read through your post and I believe the line “Now, you visit A5 and remove his rights from there.” should actually be “Now, you visit A4….” since A4 is the site with unique permissions

]]> By: SharePoint Buzz http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-7307 Mon, 13 Apr 2009 01:44:29 +0000 http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-7307 SharePoint Quick Links 05.28.07…

As krichie that sharepoint guy points out, Yep, that was ……

]]> By: SharePoint Buzz http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-7303 Mon, 13 Apr 2009 01:44:23 +0000 http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-7303 SharePoint Links 04.07.07…

There’s quite a few buzz worthy posts out in the blogosphere ……

]]> By: Carlos http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-7185 Tue, 14 Oct 2008 14:13:36 +0000 http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-7185 Confirmed, I believe a customer deleted all Limited Access rights on the top level and boom… all subfolders and items lost their permissions… I suggest DONT delete any user with limited access.

Keith, great post…thanks.

]]> By: Devster http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-6991 Wed, 09 Apr 2008 17:07:48 +0000 http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-6991 Krichie:
Great post…(and diagram) you validated that I wasnt losing my mind.

]]> By: Keith Richie http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-6429 Wed, 12 Dec 2007 19:49:24 +0000 http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-6429 Sara:
Sorry my diagram isn’t readable. I completely disagree with your statement of always giving access to something above before you give access to something below. Alot of organizations keep things higher in the heirarchy more secure and only allow users access within specifically. That’s why you see the “Limited Access” permission level on higher objects when a user has more permissions on a contained object. Limited Access is the castle key in this scenario :)

jb:
Are you just jazzing me man? Or do I have to go back and read my own poor quick blog post on this to correct it again :)

]]> By: Sara http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-6428 Wed, 12 Dec 2007 19:18:15 +0000 http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-6428 Maybe I am misunderstanding, but it seems like if you simply follow good administration practice you shouldn’t have much of a problem. If you want someone to have full access to A4, you should at least have given him read and list to A and A1 (btw it would be a little easier to understand if your hierarchy were A, A1, and A1a, A1b, or something other than another number in sequence). You should never give a user permission to something under another item without giving him some permission to the item above. It’s like giving him a key to a room in the castle without giving him a key to the castle wall.

]]> By: jb http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-5354 Fri, 05 Oct 2007 04:05:02 +0000 http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-5354 “Now, you visit A5 and remove his rights from there.” should read “Now, you visit A4 and remove his rights from there.” right? :)

]]> By: Still be aware of Cascading Deletes in WSS/MOSS « Krichie - That SharePoint Guy http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-5300 Sat, 29 Sep 2007 13:38:03 +0000 http://blog.krichie.com/2007/04/05/beware-of-cascading-deletes-in-wssmoss/#comment-5300 [...] be aware of Cascading Deletes in WSS/MOSS In my previous post, Beware of Cascading Deletes in WSS/MOSS, I noted that this was confirmed to be a bug, but after review and a few discussions with key folks [...]

]]>