All Remote System Explorer resources such as connections, user actions, filters, and filter pools are managed by profiles. When you define your first connection to a remote server, a default profile named after your workstation is created for you. Profiles help you organize information about several connections or filter pools. The Remote System Explorer creates a unique profile for each team member (your default private profile), plus a common profile called Team. You can also create new profiles if you want to use them to organize a specific set of filters and connections.
For example, you could create a profile named HR_Application to store connections, filters, and compile commands related to developing a human resources application. Then you could create another profile called OrderEntry to store connections, filters, and compile commands related to developing an order entry application as well.
Your default profile is for your local workstation. Choosing a Team profile for connections and filters assists in team support, since all connections, filter pools, and team profiles can be shared among team members. You can use the Team view to control which profiles display in your workspace by making the profiles active.
Profiles can be active, or inactive. By default, only your default private profile and the Team profile are active. The Remote System Explorer displays all connections from all active profiles and, within a connection, allows filter pools to be referenced from any active profile. Further, the user actions and compile commands shown in the pop-up menu for a remote resource are from all active profiles.