quote from Help
You can also access the Details dialog by selecting Details from the File menu.
The steps work for Files, Folders and Custom Obkects. Is that what you're asking since the steps asdie from the first statement only mentions files?
-Hywell
Well, I understand what it means to file ... But what does it mean for a folder? What effect this property to a folder?
See the Read, Modify, Delete table in the help link you supplied. If the files in the folder you are changning security on don't have any security on them, they will use the security of the folder.
Sorry byt still not clear.
Won't those files have folder's security on them in both cases: without "foder security override" and with it?
Let me try and clarify. A security override is just resetting the current security that the folder may have from a lifecycle state or from an higher level folder.
Therefore, with or without an override if the folder security is set and the files have no security, they will use the folders security setting.
A file, folder, or custom object that does not have an Access Control List defined uses role-based security. Refer to Managing Roles for more information.
Thank you for the answer Irvin
As I understand Override folder has the highest priority and will be inherited by all files and folders that are inside? A an override security objects within the folder will have priority overrated the parent folder?
Folder A
----> Sub Folder 1
----> Sub Folder 2
Scenario 1
Scenario 2
If the Administrator changes the security on Folder A
The propagte option only changes sub folder security not files. If the file's security is inherited from the folder, it will change with the propagation setting.
A user may be able to find the file using search but they will not be able to download the file because they do not have access to the folder.
Folder ACL has little meaning when the folder's files have "State Security" 🙂
Make it 😞
We use now folder security without state security and override security for the "released" files using the Job Server.
The big difference between override security and role based security is, override security will not be inherited by default. Override security settings is very useful in such scenario:
Say I have 3 groups: Administrators, Project Creators, Everyone
My folder structure is as follow:
$
---->Projects
---->Project 1
---->Project 2
...
Results:
In such way, we can prevent users from messing up our vault folder structure.
A user may be able to find the file using search but they will not be able to download the file because they do not have access to the folder.
I wish this was the case. Users CAN download/get files in folders they have no permission to. This is exactly the problem we have. We are not able to use security based lifecycle changes on the files.
We had to create a custom add-in so users can't check-out released files because of this.
We have the following structure (simplifeid):
Productgroup1
--Engineering
Productgroup2
--Engineering
Productgroup3
--Engineering
etc.
Folder security:
Members of the Viewing1 group have read only access to Productgroup1\PDF, no access to Productgroup1\Engineering
Members of the Consuming1 group have read only access to Productgroup1\PDF and Productgroup1\Engineering
Members of the Engineering1 group have read access to the PDF folder and read/write access Productgroup1\Engineering
Viewing1+Consuming1+Engineering1 do not have access to Productgroup2 and Productgroup3 etc.
The pdf files in the PDF folders are created by the Job Server
The problem is that the lifecycle security will give access to a file according the settings in the lifecycle definitions. If we want to use 1 lifecycle for Inventor files everyone will get access to files in all folders. User cannot browse to the file but can do a search, find and download the files in the folders they do not have access to.
To use the Vault for the folder structure above + lifecycles we need to create multiple Vault Lifecycles for each productgroup what will be unpossible to manage.
Lifecycles should honoured the folder security. So when a state change the lifcycle security should only apply for security settings if they are not conflicting with the folder security.