Lock down Directories
-
We have a numbered directory for every project, set up automatically when the project is accepted. There is a standard subdirectory tree. I am constantly finding project directories missing and eventually find them under another directory - someone has carelessly dragged and dropped them. I'm trying to find a solution to stop them (short of committing a major crime). So far I have thought of changing permissions on the project directory so that only the Administrator can move them, and then changing permissions on all subdirectories so that they are not inherited but Everyone has RW rights. This will be complicated to do, as staff must, on occasions, be able to create special purpose subdirectories and they will default to inheriting the folder properties. Is there a better way to lock down directories but allow access to everything below them?
-
We have a numbered directory for every project, set up automatically when the project is accepted. There is a standard subdirectory tree. I am constantly finding project directories missing and eventually find them under another directory - someone has carelessly dragged and dropped them. I'm trying to find a solution to stop them (short of committing a major crime). So far I have thought of changing permissions on the project directory so that only the Administrator can move them, and then changing permissions on all subdirectories so that they are not inherited but Everyone has RW rights. This will be complicated to do, as staff must, on occasions, be able to create special purpose subdirectories and they will default to inheriting the folder properties. Is there a better way to lock down directories but allow access to everything below them?
This is where you need to be using some sort of version control software/system. By using version control, your directory structure and contents will be versioned which means that it will be easy to trace and restore when anything changes or moves. I have seen others struggle with the same issue you are describing and they never came to a solution, however as soon as I started working in tightly version controlled environments what you describe was no longer an issue. You could create one main repository or a repository for each second level directory - the only downside is that it will take a bit to educate people and set it up but it will allow you control and transparency over actions taken of individual files.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
We have a numbered directory for every project, set up automatically when the project is accepted. There is a standard subdirectory tree. I am constantly finding project directories missing and eventually find them under another directory - someone has carelessly dragged and dropped them. I'm trying to find a solution to stop them (short of committing a major crime). So far I have thought of changing permissions on the project directory so that only the Administrator can move them, and then changing permissions on all subdirectories so that they are not inherited but Everyone has RW rights. This will be complicated to do, as staff must, on occasions, be able to create special purpose subdirectories and they will default to inheriting the folder properties. Is there a better way to lock down directories but allow access to everything below them?
How many project directories are we talking about? Are these on a Windows Server? Make each Project Directory a share that is mapped as a separate drive for each user, that will stop the top level directories bsing moved. Subdirectories can still be faarrrkkkked, but you can use Share/NTFS permissions to limit what users can screw up.
Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004