feat(Pixie integration): Moved install steps to new page with new inf…

…o about linking accounts

src/content/docs/auto-telemetry-pixie/install-auto-telemetry-pixie.mdx

@@ -10,39 +10,49 @@ redirects:
   - /docs/auto-telemetry-pixie/get-started-auto-telemetry-pixie/#install-auto-telemetry-with-pixie
 ---
 
+To get up and running with Auto-telemetry with Pixie, you start with our guided installation. This applies whether you have a Pixie account, a New Relic account, both types of accounts, or neither. The guided installation deploys Pixie with New Relic's Kubernetes integration on your cluster. You don't need to do any further configuration or installation to start using Pixie.
 
+## Setup info depends on your account status
 
+Depending on the type of account you have, the following sections provide information about the process as it applies to you.    
 
-## Start using Pixie in New Relic [#link-pixie-account]
+### You have a New Relic account, but not a Pixie account [#install-new-to-pixie]
 
+The guided install automatically sets up a Pixie account and links it to the New Relic account you select. You access the Pixie UI via New Relic's **Live debugging with Pixie** area of your Kubernetes clusters. You cannot log directly into the Pixie UI. Start the guided install at the [beginning of the process](#install-beginning).
 
-## Install Auto-telemetry with Pixie [#install-new-to-pixie]
+If you want to install Auto-telemetry with Pixie on multiple clusters, re-run the guided install for each additional cluster.
 
-Use our [guided installation](/docs/full-stack-observability/observe-everything/get-started/new-relic-guided-install-overview/) process to install Auto-telemetry with Pixie. This deploys Pixie with New Relic's Kubernetes integration on your cluster. You don't need to do any further configuration or installation to start using Pixie.
+### You have a Pixie account, but not a New Relic account [#linked-from-pixie]
 
-If you want to install Auto-telemetry with Pixie on multiple clusters, re-run the guided install for each additional cluster.
+If you follow a link to New Relic from the Pixie UI and do not have a New Relic account, you must first create one. Follow the [New Relic signup](https://newrelic.com/signup) steps to create a New Relic account. Make sure you use the same email address for both your New Relic and Pixie accounts. When you create the account, your Pixie account is linked to it. Then, continue the guided install process [with these steps](HERE).
+
+### You have a Pixie account and a New Relic account [#both-accounts]
+
+If you already have a New Relic account and a Pixie account, you can link your Pixie account with New Relic by clicking on the New Relic logo in the Pixie UI. This brings you to the [Configure the HELM command/manifest (yaml) file](#install-helm-command-manifest) section of the guided install, provided that you're using the same email address in Pixie and New Relic. 
+
+If you're using different email addresses in Pixie and New Relic, you'll have to make one of these changes:
+* Use the New Relic guided installation to migrate your Kubernetes clusters to a new Pixie account.
+* Use the email you used for your Pixie login to creat a new New Relic account, log into New Relic with that email address, and then click the New Relic logo in Pixie.
+* Contact support to manually link your existing Pixie account with your New Relic account.
 
-### Before you begin
+
+## General prerequisites before you link New Relic and Pixie [#general-prereqs]
 
 * Review this [Pixie data security overview](/docs/auto-telemetry-pixie/pixie-data-security-overview) for actions to take to secure your data.
 * Make sure you have sufficient memory: Pixie requires 2Gb of memory per node in your cluster.
 * Review the other [Pixie technical requirements](https://docs.px.dev/installing-pixie/requirements/).
 * You must be a [full user](/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure/#user-type). Other user-related requirements: 
-  * For users on [original user model](/docs/accounts/original-accounts-billing/original-product-based-pricing/overview-changes-pricing-user-model/#user-models): cannot be a [Restricted User](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/#roles).
-  * For users on [New Relic One user model](/docs/accounts/original-accounts-billing/original-product-based-pricing/overview-changes-pricing-user-model/#user-models): must be assigned to a [group](/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure/#groups) that has a role with Pixie-related [capabilities](/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure/#capabilities). 
-
-<Callout variant="important">
-If you are already a Pixie user, you must still install using the guided installation steps described below. This will provide the API keys that you need.
-</Callout>
+  * Users on our [original user model](/docs/accounts/original-accounts-billing/original-product-based-pricing/overview-changes-pricing-user-model/#user-models) cannot be [Restricted](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/#roles).
+  * Users on our [New Relic One user model](/docs/accounts/original-accounts-billing/original-product-based-pricing/overview-changes-pricing-user-model/#user-models) must be assigned to a [group](/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure/#groups) that has a role with Pixie-related [capabilities](/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure/#capabilities). 
 
-### Install from the beginning of the guided install process
+## Install from the beginning of the guided install process [#install-beginning]
 
 1. Open our [New Relic One guided install](https://one.newrelic.com/launcher/nr1-core.explorer?pane=eyJuZXJkbGV0SWQiOiJucjEtY29yZS5saXN0aW5nIn0=&cards[0]=eyJuZXJkbGV0SWQiOiJucjEtaW5zdGFsbC1uZXdyZWxpYy5ucjEtaW5zdGFsbC1uZXdyZWxpYyIsImFjdGl2ZUNvbXBvbmVudCI6IlZUU09LdWJlcm5ldGVzIiwiYWN0aXZlRW52aXJvbm1lbnQiOiJrdWJlcm5ldGVzIiwicGF0aCI6bnVsbCwiZW52Ijoia3ViZXJuZXRlcyJ9).
 2. Select the account you want to use for the guided install, and click **Continue**.
    Note: if you have a single account, you won't see this option.
 3. Select **Kubernetes** and then continue with step one in the next section.
 
-### Install from the Configure the HELM command/manifest (yaml) file 
+## Install from the Configure the HELM command/manifest (yaml) file [#install-helm-command-manifest]
 
 If you arrived in the guided installation process by following a link from Pixie or from within New Relic, your steps begin here. 
 
@@ -78,4 +88,8 @@ If you arrived in the guided installation process by following a link from Pixie
 5. Click **Continue** to open the **Listening for data** page. 
 6. When you get the message, **See your data**, click **Kubernetes Cluster Explorer** to see your cluster. 
 
-  Auto-telemetry with Pixie might restart after installation. This is caused by the auto update feature.
+  Auto-telemetry with Pixie might restart after installation. This is caused by the auto update feature.
+
+### If you link the wrong Pixie and New Relic account [#link-wrong-accounts]
+
+Contact support to unlink a Pixie account from your New Relic account. Be aware that if you unlink a Pixie account that was created automatically through the guided install, you'll lose access to that Pixie account.