Although access rights can be set on individual items, this is rarely done. For example, if you really need to allow only one person to know about a particular file, you can give only that person access rights to that file. However, by default, the owner of the file and anyone belonging to a group with the correct privileges can still see that file.
To ensure that only that one person can access the file, you would have to stop the StarTeam Server from checking for privileges. Then the access to every object would be controlled solely by access rights.
Like folders, items in a child view retain the access rights they had in the parent view until they branch into new objects. Items lose their access rights only when branching.
When you share a folder or item, the access rights set for it at the folder or item level accompany it, until the folder or item branches.
When you share a folder or item, its behavior may change. When shared, the behavior immediately becomes able to branch on change, even if the Branch On Change check box was disabled in the original location. Whether the Branch On Change check box is selected or cleared depends on the property setting for the destination view Set Items That Are Shared Into View To Branch On Change.
When the folder or item branches in its new location, a new object is created in the repository, and that new object initially has no access rights at the folder or item level.