Can anyone tell me how to remove access to a folder? I am in a situation where I am migrating information from my Livelink System however; I need to keep the information on Livelink in a static state. I have tried to remove access to the folders and have hidden the folders but none of the things I have tried keep the users from accessing the information especially when they have shortcuts setup. This has allowed documentation that I have already processed to be modified... I can't just remove user permissions as it is time consuming and these users still have to access other folders within the same branch...
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How do I "Remove" Access to a Folder 1
- Thread starter Boham
- Start date
-
1
- #2
to answer your qn having gone thru this in a similar way the easy way is far from being available.If the livelink user DB can be made readonly then truly your users will be prevented from doing it.Note every user transcation that tries to do modify will get a severe error and the users will be none too happy about it.I am not even sure if this is possible since I do not psess dba knowledge.However here are things that we use to do in a similar situation.You could make the EFS readonly that also will error out and confuse the users terribly.
a)We maintain a livelink by cloning our production DB.Then in bold RED LETTERS WE SAY ON THAT.THIS IS A READONLY SYETM AND YOU ARE BY YOURSELF IF YOU MODIFY IT.
b)We temporarily using Object & Usage privileges restrict creation of folders,documents etc.this would mean that they still will be able to modify things that they had access to.
c)Keep all users login disabled and ask them to use a hard coded guest account.They will see thir items but since the guest user does not get to do any revisioning you are going to be safe.Note creation of the guest account means that you have to hardcode the userid/apssword in your URL so security people may not like that.
By far approach A works in 90 % of situations.
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer and probably certfiable,Livelink ECM Champion 2008
a)We maintain a livelink by cloning our production DB.Then in bold RED LETTERS WE SAY ON THAT.THIS IS A READONLY SYETM AND YOU ARE BY YOURSELF IF YOU MODIFY IT.
b)We temporarily using Object & Usage privileges restrict creation of folders,documents etc.this would mean that they still will be able to modify things that they had access to.
c)Keep all users login disabled and ask them to use a hard coded guest account.They will see thir items but since the guest user does not get to do any revisioning you are going to be safe.Note creation of the guest account means that you have to hardcode the userid/apssword in your URL so security people may not like that.
By far approach A works in 90 % of situations.
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer and probably certfiable,Livelink ECM Champion 2008
- Status
Similar threads
