# Team support

The team support model works with shared repositories that store version-managed resources on servers that are accessible to the entire team. Usually you would share the folders and files of an Eclipse project. Each team member sends their changes to the repository, and receives changes that were made by a team member from the repository. While the Remote System Explorer is not project-based, (it is designed for direct access to remote resources), there is a single project created for all the non-remote resources that the Remote System Explorer manages. Profiles are stored in that project and so everything that belongs to a profile can be shared with your teammates.

Profiles contain:

- Connections -- including various subsystem properties. User IDs and passwords are not shared.
- Filters, filter pools, and filters pool references
- User-defined actions
- Compile commands

Use the Team view of the Remote System Explorer perspective to associate and synchronize the project named RemoteSystemsConnection that contains these profiles with a repository. After synchronizing with the repository, you will receive all the shared Remote System Explorer resources from your team, including their profiles. You then use the Reload Remote System Explorer action, located on the pop-up menu, to make the Remote System Explorer know about these changes. You can also, of course, quit and restart the workbench. See the related tasks for more information.

Any resources received that are in a profile that you have already active, such as Team, will immediately be available and accessible to you. However, resources in other profiles will not be available unless you choose to make those profiles active. If you use multiple workstations, team support can also be used to make your own private configurations of filters, filter pools, and connections available on all the workstations by making your profile active on each workstation.