I read you regularly and usually find answers to my questions. Not this time, unfortunately.
I recently shared a library of screws. (The box grows, I'm no longer alone.) At the same time, I took the time to write a procedure for using and modifying this library. Unfortunately, a black sheep refuses to follow the procedures and I find myself with erroneous screws, modified nomenclatures, additions that are not used here,... So I'd like to know if it's possible to completely block this folder from writing. While keeping the possibility of importing our fasteners in several solidworks assemblies?
@Gt22: making the library read-only is not enough, if the user has the right to modify this, nothing prevents him from going to the properties of the folder and removing it:)
It is therefore necessary to limit the rights for a user or a group.
The library had of course been created to avoid all the problems of the toolbox version, the links that could have been with it have been removed,... In addition, we use very little screws. So I have a library of about 30 references. Much easier to find your way around.
All cartoonists have the same rights on the network (writing, because we work in a network). But with your leads, I'm going to contact our computer scientist so that he can block writing with his Admin access.
I think that will have to do the trick. It will be a bit restrictive to contact him every time we have to modify or add a reference, but it will save me from going to check all the files every morning.
I think that if you are many and or bring to be. It would be interesting to have a person referring to the BE who has a higher right than the others.
For example, for shared templates and files, your IT person could provide this person with the necessary rights. This would avoid contacting a network admin for each change.
@Yves.T: Of course: The problem is that for the network admin it quickly becomes very complicated if you manage the rights by folder and by user. Especially if the IT department is outsourced (which seems to be the case)
Yes, Remrem, I think I'm talking to the management about it, in order to give a person the rights. But by the time the decision is made, I'll have to go through the IT specialist. (Indeed, it's an external who only comes when we scream for help. ;-) )
And it's in order not to make it change the rights of several PCs/users that I was thinking of putting the common files on another partition of the server in order to make it easier for it. But he will choose the simplest solution for him/the most suitable for our needs.
Yves, yes, I know, I just tested, and I have the right to deny write access to a specific folder, but other cartoonists, who have the same access as me, have the right to re-enable write access as well. So it's not definitively "blocked" as we would like.
Hence the fact that I will have to ask the computer scientist to make some changes on the network. We grew very quickly and went from 1 to 4 cartoonists, in 1 month. So it's still a bit complex for us to manage. It's no longer the same management of the network, of the works,... It requires a bit of adaptation.
Thank you for your super quick answers in any case.
It is possible to create a group with and a group without rights. By doing this, you can then define which group is entitled to what on a file, folder, or disk.
Talk to your IT specialist, he will be able to advise you.
PS: it is also possible to assign a user to several groups.
User rights management is not simple at its core, but it becomes necessary when a company grows.