Hi, hopefully this is the best forum for this question.
We have a network share which retains folders/files for different Projects, within the root of the share (which all team have access) is a folder for each Project. Each project has it's own team members, which can change frequently, so we allow the team members to manage access to the project folders themselves. The projects contain sensitive information so we implement least privileges (Chinese Walls in effect), only the owner of the folder can grant access to other project team members.
To implement the permissions, we use the same template as recommended for roaming profiles. However we've run into a little difficulty. If another team member other than the folder owner creates a file within the project folder, the folder owner does not have permissions to see or access the file; however all other team members have access as expected. This is because we have granted the folder owner full access when they create the folder, and the permissions are associated with the owner only. So when another user creates a file they become the owner of that file, therefore the folder owner no longer has explicit access to that file.
For an example situation:
\Project Folder\ (User A {Owner}, User B {Explicitly Added}; User A creates project folder, adds User B with access)
\Project Folder\file1.txt (User A {Owner}, User B {Inherited Access}; User A creates a file, User B can access it through inherited access)
\Project Folder\file2.txt (User B {Owner & Inherited Access}; user B creates a file, User A has no access)
Is there a way to tweak the folder permissions so that the folder owner can still have access to all files created within their project? We need a permission structure that would enable a user to create a folder within the share root and only they have access to that folder + any project team members they specify after creation.
Thanks,
Jay :)
If you shake a kettle, does it boil faster?