Configure Ship Node Access

About this task

From the Team Details window, select the Ship Node Access tab and perform one of the following tasks to configure the ship node access for a team:

For more information about configuring ship node access, refer to the Configuring system-wide settings.

The following figure illustrates the hierarchy of organizations. In this illustration, E1, E2, and E3 are organizations that are modeled as enterprises. N1, N2, N3, N4, N5, and N6 are organizations that are modeled as nodes.

Figure 1. Organizational Hierarchy

Enterprise E1 is the parent organization of nodes N5 and N6, and enterprises E2 and E3. Enterprise E2 is the parent organization of nodes N1 and N2. Enterprise E3 is the parent organization of nodes N3 and N4.

The following figure illustrates the hierarchy of organizations that are administered by other organizations.

Figure 2. Administered By Organizations

Nodes N1 and N2 are administered by enterprise E2. Nodes N3 and N6 are administered by enterprise E1. Node N5 is administered by enterprise E3. Enterprise E3 is administered by enterprise E2, and enterprise E2 is administered by enterprise E1.

The following examples explain the ship node access policy based on the Organization Hierarchy and Administered By Organization illustrations. Assume that for each organization, the administrator has created a team.

Example 1:

About this task

When ship node access is configured to User's Node in all the team configurations.

Organization E1 E2 E3 N1 N2 N3 N4 N5 N6
Nodes accessible to the users associated to a team N1 N1 N3 N1 N2 N3 N4 N5 N6
N2 N2 N4            
N3                
N4                
N5                
N6                

Users of Enterprise E1 will have access to nodes N1 through N6 because the parent organization of these nodes are either the user's enterprise or an enterprise that is hierarchically lower than the user's enterprise.

Users of Enterprise E2 will have access to nodes N1 and N2.

Node users will have access to only their own organizations.

Example 2:

About this task

The following organizations' ship node access is configured as mentioned here:

  • E1 - Restrict Access to Nodes N1 and N5
  • E2 - Nodes Accessible To Team Creator
  • E3 - All Nodes
  • N1, N3 - Nodes Accessible To Team Creator
  • N2, N4 - User's Node
  • N5 - Restrict Access to Nodes N1 and N4
  • N6 - Restrict Access to Nodes N2 and N3
    Organization E1 E2 E3 N1 N2 N3 N4 N5 N6
    Nodes accessible to the users associated to a team N1 N1 N1 N1 N2 N1 N4 N1 N2
    N5 N5 N2 N5   N5   N4 N3
        N3            
        N4            
        N5            
        N6            

The ship node access for the users of enterprise E1 is limited to nodes N1 and N5.

Users of enterprise E2 have access to nodes N1 and N5 because they are the only nodes that are accessible to the creator of the team, who belongs to enterprise E1.

Users of enterprise E3 have access to all the nodes because the team configurations is set to All Nodes.

Users of node N1 have access to those nodes that are accessible to users belonging to enterprise E2. Similarly, users of node N3 have access to those nodes that are accessible to users of enterprise E1.