Permissions - snapshots
In RTC 3.0.1, the Team Configuration Permssions for snapshots are ambigious. There's an entry:
Save Snapshot - with two sub entries. The 2nd one, "Modify Name and Description" appears to also control "create"; is this correct? And, under Save Stream / Modify / Stream, there is: "Create and Delete Snapshots". If a person creates a snapshot in their privately-owned repository workspace, is it correct that none of these permission settings are used (because it's in their own private repository workspace, not in a shared stream)? If a person creates a snapshot in their privately-owned repo-ws, and then changes the owner of this to a shared stream, does the "Save Stream /Modify / Stream/ Create and Delete Snapshots" permission need to be true for some role that the person has? (In other words, is changing ownership of an existing snapshot considered "creating" it?). If a person has a role with the "Save Stream / Modify / Stream/ Create and Delete Snapshots", but does not have permission under "Save Snapshot / Delete Snapshot", does that prevent them from deleting a snapshot? Thanks for clearing this up! Our goal is to set things up to reliably preserve certain snapshots. |
One answer
I did some experimentation. It appears:
1) none of these permissions applies to repository Workspaces - you can create / delete snapshots without these permissions. 2) The permission "Save Snapshot" can be unchecked, and you can still create a snapshot in a repository Workspace, and then change its owner to the shared stream. That is not controlled by this permission, but is controlled by the permission "Save Stream / Modify / Stream /Create and Delete Snapshots. 3) If you don't have the Save Snapshots / Delete Snapshots permission, then even though you have the Save Stream / Modify /Stream/Create and Delete Snapshots permission, you cannot delete the snapshot in the stream. If this is not correct, please let me know :-) |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.