One of my other devs needs access to a project to work on. I can't allow him access to the folder structure that it resides in so I shared the project into a folder he does have access. I set the permissions on the folder that's shared in his area but he cannot access it unless I also set the permissions for him to access the project in the source/original project location.
If I set folder permissions on one, should they apply to both? Why did setting folder permissions on the share he can view NOT grant him access? Only when I gave him RCA permissions in the source folder of the share, original location, did he then access what he needed.
Shared Folders - Permissions (4.0.4)
Moderator: SourceGear
Shared Folders - Permissions (4.0.4)
Neal Culiner
NC Software, Inc.
http://www.nc-software.com
Vault 5.1.2
VS 2010/C#
Windows 7 Ultimate x64
VB.NET Forums: http://www.vbdotnetforums.com
NC Software, Inc.
http://www.nc-software.com
Vault 5.1.2
VS 2010/C#
Windows 7 Ultimate x64
VB.NET Forums: http://www.vbdotnetforums.com
Any modifications to a shared folder will also change contents the linked folders. So if a user has only R access to a folder, it makes sense that any share would also have R so that no changes can be made.
In your case, it sounds like it's OK for the user to modify the shared folder, but not have access to other parts of the directory structure. I'll log a feature request to deal with this type of situation.
In the meantime, would a branch work for the developer?
In your case, it sounds like it's OK for the user to modify the shared folder, but not have access to other parts of the directory structure. I'll log a feature request to deal with this type of situation.
In the meantime, would a branch work for the developer?
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
No, a branch would not work as far as I know.
To repeat:
I have an area that contains a project that a dev cannot access as it contains other projects. So I SHARED this project to his working area:
PrivateArea
--Branches
--Trunk
----Project1
----Project2
----ProjectToshare
DevsArea
--Branches
--Trunk
----DevProj1
----DevProj2
----LinkedProj
In the example above "ProjectToshare" is private, he does not have access to this. In "LinkedProj" I gave him RCA. However, he could NOT access this project until I changed ProjectToshare to RCA. So it seems that the permissions are not isolated as it should be but depends on the permissions of ProjectToshare - aka a bug, not a feature request.
Thank you.
To repeat:
I have an area that contains a project that a dev cannot access as it contains other projects. So I SHARED this project to his working area:
PrivateArea
--Branches
--Trunk
----Project1
----Project2
----ProjectToshare
DevsArea
--Branches
--Trunk
----DevProj1
----DevProj2
----LinkedProj
In the example above "ProjectToshare" is private, he does not have access to this. In "LinkedProj" I gave him RCA. However, he could NOT access this project until I changed ProjectToshare to RCA. So it seems that the permissions are not isolated as it should be but depends on the permissions of ProjectToshare - aka a bug, not a feature request.
Thank you.
Neal Culiner
NC Software, Inc.
http://www.nc-software.com
Vault 5.1.2
VS 2010/C#
Windows 7 Ultimate x64
VB.NET Forums: http://www.vbdotnetforums.com
NC Software, Inc.
http://www.nc-software.com
Vault 5.1.2
VS 2010/C#
Windows 7 Ultimate x64
VB.NET Forums: http://www.vbdotnetforums.com
And how can I tell in Vault's Client GUI which one is the linked and which is the "source". They both look the same to me as I cannot tell which is linked from the other.
Neal Culiner
NC Software, Inc.
http://www.nc-software.com
Vault 5.1.2
VS 2010/C#
Windows 7 Ultimate x64
VB.NET Forums: http://www.vbdotnetforums.com
NC Software, Inc.
http://www.nc-software.com
Vault 5.1.2
VS 2010/C#
Windows 7 Ultimate x64
VB.NET Forums: http://www.vbdotnetforums.com