Share broken in a readonly folder

[Brody]

A developer recently broke a share in a folder that he had read only permision in.

By broke, I mean that he turned the share into a branch even though he only had read permisions in the folder.

Surely this cannot be correct behaviour. Please advise if it can be undone or am I up for a delete and reshare.

[lbauer]

What version of Vault are you using?

Does the user have any rights that might have been set explicitly or inherited from group at a higher level? In the Vault Admin Web Client->Users, click Overview for a listing of that user's rights.

[Brody]

I have found the cause and I think it is a bug.

If a developer has permissions anywhere in the repository to a file then they can affect that file in a folder they do not have permission to change.

In our example, a developer has accidently branched from a share (instead of sharing) a file in a folder they had read permisisons for only. They also have RCA permissions for that file in another folder. This has allowed them to make a change in a folder they do not have permission to change and break my share (Which is a pain because I can't roll back that change and get the share back.)

They should not be able to change that file in that folder. Hopefully you can see my problem and hopefully it is a bug that can be fixed. If it is by design then I'll need you to tell me why because that seems wrong.

Thanks

Brody

[lbauer]

Thanks for the details. We would like to try to reproduce this here. What version of Vault are you using?

[Brody]

We are using 5.0.1 to 5.0.4.

[lbauer]

Let me make sure I understand this. The developer has RCA rights to Folder A, and R rights to Folder B. There is a file that is shared between Folder A and Folder B.

The developer can branch the share from Folder A, leaving an unshared file in Folder B.

Is that the right scenario?