(workflow) updated IPH with QG graphics

Vantage/cgh1722901880213.md

@@ -2,29 +2,34 @@
 
 When connecting a VantageCloud Lake environment as a data source, QueryGrid must be deployed on both environments and visible on the same VantageCloud Lake console.
 
-Before you begin, chose which environment will be the source environment and which will be the target environment. Both VantageCloud Lake data sources must be on the same platform, for instance, VantageCloud Lake on AWS can only connect to VantageCloud Lake on AWS, not another cloud provider.
-
 ## New data source
 
 
-1.  From the source environment, select **Manage data** > **QueryGrid** > **Data sources** tab.
+1.  Select which VantageCloud Lake environment will be the source environment and which will be the target environment.
+
+    Both VantageCloud Lake data sources must be on the same platform, for instance, VantageCloud Lake on AWS can only connect to VantageCloud Lake on AWS, not another cloud provider.
+
+
+1.  From the source environment, select **Manage data** > **QueryGrid**.
 
 
-1.  Select ![""](Images/gdy1625181386091.png) to add a data source.
+1.  From the **Data sources** tab, select ![""](Images/gdy1625181386091.png) to add a data source.
 
 
-1.  Select VantageCloud Lake.
+1.  Select VantageCloud Lake as the target data source.
 
+    ![QueryGrid data source](Images/euj1724287834509.png)
 
-1.  Select target environment from the menu and then **Next**.
+
+1.  Select the target environment from the **Select VantageCloud Lake environment** menu and then select **Next**.
 
 
 ## Private link
 
 
 Enter the DNS address provided from the support ticket created previously and select **Next**.
 
-The secondary IP address will be using the **Data source details** step.
+The secondary IP address will be used in the **Data source details** step.
 
 ## Data source details
 
@@ -37,7 +42,7 @@ The secondary IP address will be using the **Data source details** step.
 1.  Select the cloud platform and region where the target system is located, for example AWS and US West (Oregon).
 
 
-1.  Enter the secondary IP of the target system, provided from the support ticket created previously, under **Connector properties**.
+1.  Under **Connector properties**, enter the secondary IP of the target system, provided from **PrivateLink** step.
 
 
 1.  Select **Next**.
@@ -48,6 +53,8 @@ The secondary IP address will be using the **Data source details** step.
 
 The nodes automatically register themselves when you get to this step. Select **Next** once the registration is completed.
 
+![QueryGrid node registration](Images/rlr1724288508418.png)
+
 ## Network diagnostics
 
 
@@ -61,7 +68,9 @@ Start the diagnostics and wait for it to complete before selecting **Next**.
     This is the password that was provided when the environment was first provisioned.
 
 
-1.  Start the diagnostics and wait for it to complete before selecting **Next**.
+1.  Select **Start diagnostics** to run the test and wait for it to complete before selecting **Next**.
+
+    ![QueryGrid connector diagnostics](Images/rlm1724288803062.png)
 
 
 ## Authorization
@@ -71,3 +80,5 @@ Select **Learn** more to see the available authorization options and decide what
 
 You can optionally select **Skip authorization** and then **Finish** to complete it at a later time.
 
+![QueryGrid connector authorization](Images/imr1724288993792.png)
+

Vantage/ruf1680184116601.md

@@ -30,5 +30,7 @@ Use restricted groups from your identity provider to limit access to the realm.
 
 You can map the VantageCloud Lake predefined roles to the groups in your IdP or database users in the VantageCloud Lake console to define their access. Map all roles to either database users or IdP groups. Mapping a subset of roles to both is not supported. See [Role-Based Access Control (RBAC)](https://docs.teradata.com/access/sources/dita/topic?dita:topicPath=jzo1722836167532.dita).
 
+---
+
 **Next:** [Associate the realm with environments](jbj1680184191443.md)