When you are working on your own, your repository workspace contains only your work. Changes you check in are backed up to the repository and can be preserved in baselines and snapshots or aggregated in streams, but change flow is unimportant, since there are no other team members with whom to collaborate. In a team environment, change flow becomes an important part of your everyday work. It supports efficient collaboration, hierarchical integration, and iterative development. Setting up your repository workspaces with the proper contents and flow targets is the first step toward making your contributions to the team's efforts.
One of the first things that a team member does is to "join" one or more of the team's streams by creating repository workspaces from them. It is also possible to create an empty repository workspace that you can configure with components that you select from other streams or repository workspaces, or that you share from your Eclipse workspace or sandbox.
Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug