fix: update dashboard URLs for v2 UI migration

authentication/email.mdx

@@ -206,7 +206,7 @@ const response = await client.emailAuth({
   <Card title="Auth Proxy Users" icon="server">
     **Affected:** Anyone using Auth Proxy without `appName` set
 
-    **Action:** Set `appName` under [email configuration](https://app.turnkey.com/dashboard/walletKit)
+    **Action:** Set `appName` under [email configuration](https://app.turnkey.com/dashboard/v2/wallet-kit)
   </Card>
   <Card title="Server SDK Users" icon="code">
     **Affected:** Users calling `init_otp_auth`, `init_otp`, `email_recovery`, or `email_auth` without `appName`

concepts/policies/smart-contract-interfaces.mdx

@@ -227,7 +227,7 @@ Let's walk through an example flow of how to explicitly reference smart contract
 [{"constant":true,"inputs":[],"name":"name","outputs":[{"name":"","type":"string"}],"payable":false,"stateMutability":"view","type":"function"},{"constant":false,"inputs":[{"name":"guy","type":"address"},{"name":"wad","type":"uint256"}],"name":"approve","outputs":[{"name":"","type":"bool"}],"payable":false,"stateMutability":"nonpayable","type":"function"},{"constant":true,"inputs":[],"name":"totalSupply","outputs":[{"name":"","type":"uint256"}],"payable":false,"stateMutability":"view","type":"function"},{"constant":false,"inputs":[{"name":"src","type":"address"},{"name":"dst","type":"address"},{"name":"wad","type":"uint256"}],"name":"transferFrom","outputs":[{"name":"","type":"bool"}],"payable":false,"stateMutability":"nonpayable","type":"function"},{"constant":false,"inputs":[{"name":"wad","type":"uint256"}],"name":"withdraw","outputs":[],"payable":false,"stateMutability":"nonpayable","type":"function"},{"constant":true,"inputs":[],"name":"decimals","outputs":[{"name":"","type":"uint8"}],"payable":false,"stateMutability":"view","type":"function"},{"constant":true,"inputs":[{"name":"","type":"address"}],"name":"balanceOf","outputs":[{"name":"","type":"uint256"}],"payable":false,"stateMutability":"view","type":"function"},{"constant":true,"inputs":[],"name":"symbol","outputs":[{"name":"","type":"string"}],"payable":false,"stateMutability":"view","type":"function"},{"constant":false,"inputs":[{"name":"dst","type":"address"},{"name":"wad","type":"uint256"}],"name":"transfer","outputs":[{"name":"","type":"bool"}],"payable":false,"stateMutability":"nonpayable","type":"function"},{"constant":false,"inputs":[],"name":"deposit","outputs":[],"payable":true,"stateMutability":"payable","type":"function"},{"constant":true,"inputs":[{"name":"","type":"address"},{"name":"","type":"address"}],"name":"allowance","outputs":[{"name":"","type":"uint256"}],"payable":false,"stateMutability":"view","type":"function"},{"payable":true,"stateMutability":"payable","type":"fallback"},{"anonymous":false,"inputs":[{"indexed":true,"name":"src","type":"address"},{"indexed":true,"name":"guy","type":"address"},{"indexed":false,"name":"wad","type":"uint256"}],"name":"Approval","type":"event"},{"anonymous":false,"inputs":[{"indexed":true,"name":"src","type":"address"},{"indexed":true,"name":"dst","type":"address"},{"indexed":false,"name":"wad","type":"uint256"}],"name":"Transfer","type":"event"},{"anonymous":false,"inputs":[{"indexed":true,"name":"dst","type":"address"},{"indexed":false,"name":"wad","type":"uint256"}],"name":"Deposit","type":"event"},{"anonymous":false,"inputs":[{"indexed":true,"name":"src","type":"address"},{"indexed":false,"name":"wad","type":"uint256"}],"name":"Withdrawal","type":"event"}]
 ```
 
-We'll first navigate to the Security tab of your [Turnkey dashboard](https://app.turnkey.com/dashboard/welcome):
+We'll first navigate to the Security tab of your [Turnkey dashboard](https://app.turnkey.com/dashboard/v2/wallets):
 
 <Frame>
   <img

cookbook/aave.mdx

@@ -18,7 +18,7 @@ The first step is to set up your Turnkey organization and account. By following
 - A root user with a public/private API key pair within the Turnkey parent organization
 - An organization ID
 
-The next step is to create another non-root user within the organization with a different API key and exclude it from the root quorum. If you would like to remove a root user from root quorum, you can do this from the Turnkey [dashboard](https://app.turnkey.com/dashboard/security/updateRootQuorum) or [API](https://docs.turnkey.com/api-reference/activities/update-root-quorum).
+The next step is to create another non-root user within the organization with a different API key and exclude it from the root quorum. If you would like to remove a root user from root quorum, you can do this from the Turnkey [dashboard](https://app.turnkey.com/dashboard/v2/users/root-quorum) or [API](https://docs.turnkey.com/api-reference/activities/update-root-quorum).
 Here's a simple [script](https://github.com/tkhq/sdk/blob/main/examples/kitchen-sink/src/sdk-server/updateRootQuorum.ts) that shows how to update the root quorum using @turnkey/sdk-server.
 
 Finally, make sure you have a wallet with an Ethereum account created within this organization and have it funded with some ETH and USDC on Base Mainnet.

cookbook/morpho.mdx

@@ -18,7 +18,7 @@ The first step is to set up your Turnkey organization and account. By following
 - A root user with a public/private API key pair within the Turnkey parent organization
 - An organization ID
 
-The next step is to create another user within the organization with a different API key and remove it from the root quorum. You can do this from the Turnkey [dashboard](https://app.turnkey.com/dashboard/security/updateRootQuorum) or [API](https://docs.turnkey.com/api-reference/activities/update-root-quorum). 
+The next step is to create another user within the organization with a different API key and remove it from the root quorum. You can do this from the Turnkey [dashboard](https://app.turnkey.com/dashboard/v2/users/root-quorum) or [API](https://docs.turnkey.com/api-reference/activities/update-root-quorum). 
 Here's a simple [script](https://github.com/tkhq/sdk/blob/main/examples/kitchen-sink/src/sdk-server/updateRootQuorum.ts) that shows how to update the root quorum using @turnkey/sdk-server.
 
 Finally, make sure you have a wallet with an Ethereum account created within this organization and have it funded with some ETH and USDC on Base Mainnet.

cookbook/yieldxyz.mdx

@@ -37,7 +37,7 @@ Follow the [Turnkey Quickstart](https://docs.turnkey.com/getting-started/quicks
 - **Wallet** – hierarchical deterministic (HD) wallet having at least an Ethereum wallet account.
 - **Turnkey Client & Signer** – initialize a Turnkey client (`TurnkeyClient`) with your API key pair and connect a signer (`TurnkeySigner`) from `@turnkey/ethers` to your RPC provider.
 
-After creating a non-root user with a different API key, the next step is to remove it from the root quorum. You can do this from the Turnkey [dashboard](https://app.turnkey.com/dashboard/security/updateRootQuorum) or [API](https://docs.turnkey.com/api-reference/activities/update-root-quorum). Here’s a simple [script](https://github.com/tkhq/sdk/blob/main/examples/kitchen-sink/src/sdk-server/updateRootQuorum.ts) that shows how to update the root quorum using `@turnkey/sdk-server`.
+After creating a non-root user with a different API key, the next step is to remove it from the root quorum. You can do this from the Turnkey [dashboard](https://app.turnkey.com/dashboard/v2/users/root-quorum) or [API](https://docs.turnkey.com/api-reference/activities/update-root-quorum). Here’s a simple [script](https://github.com/tkhq/sdk/blob/main/examples/kitchen-sink/src/sdk-server/updateRootQuorum.ts) that shows how to update the root quorum using `@turnkey/sdk-server`.
 
 Also, make sure you have a wallet with an Ethereum account created within this organization and have it funded with some ETH and USDC on Base Mainnet.
 

docs.json

@@ -1011,13 +1011,13 @@
       },
       {
         "label": "Login",
-        "href": "https://app.turnkey.com/dashboard/auth/login?step=1"
+        "href": "https://app.turnkey.com/dashboard/v2/auth/login?step=1"
       }
     ],
     "primary": {
       "type": "button",
       "label": "Get started",
-      "href": "https://app.turnkey.com/dashboard/auth/initial"
+      "href": "https://app.turnkey.com/dashboard/v2/auth/initial"
     }
   },
   "footer": {

embedded-wallets/code-examples/add-credential.mdx

@@ -11,7 +11,7 @@ Begin by initializing the Turnkey SDK by passing in a config object containing:
 
 * `rpId`: The [Relying Party](https://developer.mozilla.org/en-US/docs/Glossary/Relying_party) Identifier, which is the effective domain of your application.
 * `apiBaseUrl`: The base URL of the Turnkey API: `https://api.turnkey.com`
-* `defaultOrganizationId`: Your parent organization ID, which you can find in the [Turnkey dashboard](https://app.turnkey.com/dashboard).
+* `defaultOrganizationId`: Your parent organization ID, which you can find in the [Turnkey dashboard](https://app.turnkey.com/dashboard/v2).
 
 <Accordion title="What's the purpose of the rpId?">
 

embedded-wallets/code-examples/create-sub-org-passkey.mdx

@@ -53,7 +53,7 @@ export default function RootLayout({
 }
 ```
 <Note>
-  The `NEXT_PUBLIC_ORGANIZATION_ID` should be set to the parent organization ID which can be found in the [Turnkey Dashboard](https://app.turnkey.com/dashboard).
+  The `NEXT_PUBLIC_ORGANIZATION_ID` should be set to the parent organization ID which can be found in the [Turnkey Dashboard](https://app.turnkey.com/dashboard/v2).
 
   The `NEXT_PUBLIC_TURNKEY_RP_ID` should be set to your application's desired relying party ID; this is typically your domain, or localhost if developing locally. See [this page](/authentication/passkeys/options#rp) for more details.
 </Note>
@@ -70,7 +70,7 @@ const turnkeyBrowser = new Turnkey({
 });
 ```
 <Note>
-  The `TURNKEY_ORGANIZATION_ID` should be set to the parent organization ID which can be found in the [Turnkey Dashboard](https://app.turnkey.com/dashboard).
+  The `TURNKEY_ORGANIZATION_ID` should be set to the parent organization ID which can be found in the [Turnkey Dashboard](https://app.turnkey.com/dashboard/v2).
 
   The `TURNKEY_RP_ID` should be set to your application's desired relying party ID; this is typically your domain, or localhost if developing locally. See [this page](/authentication/passkeys/options#rp) for more details.
 </Note>

embedded-wallets/code-examples/email-recovery.mdx

@@ -59,7 +59,7 @@ export default function RootLayout({
 }
 ```
 <Note>
-  The `NEXT_PUBLIC_ORGANIZATION_ID` should be set to the parent organization ID which can be found in the [Turnkey Dashboard](https://app.turnkey.com/dashboard).
+  The `NEXT_PUBLIC_ORGANIZATION_ID` should be set to the parent organization ID which can be found in the [Turnkey Dashboard](https://app.turnkey.com/dashboard/v2).
 
   The `NEXT_PUBLIC_TURNKEY_RP_ID` should be set to your application's desired relying party ID; this is typically your domain, or localhost if developing locally. See [this page](/authentication/passkeys/options#rp) for more details.
 </Note>
@@ -76,7 +76,7 @@ const turnkeyBrowser = new Turnkey({
 });
 ```
 <Note>
-  The `TURNKEY_ORGANIZATION_ID` should be set to the parent organization ID which can be found in the [Turnkey Dashboard](https://app.turnkey.com/dashboard).
+  The `TURNKEY_ORGANIZATION_ID` should be set to the parent organization ID which can be found in the [Turnkey Dashboard](https://app.turnkey.com/dashboard/v2).
 
   The `TURNKEY_RP_ID` should be set to your application's desired relying party ID; this is typically your domain, or localhost if developing locally. See [this page](/authentication/passkeys/options#rp) for more details.
 </Note>

embedded-wallets/code-examples/wallet-auth.mdx

@@ -10,7 +10,7 @@ description: "In this guide, we'll explore how to leverage the `WalletClient` in
 Begin by initializing the Turnkey SDK by passing in a config object containing:
 
 - `apiBaseUrl`: The base URL of the Turnkey API: `https://api.turnkey.com`.
-- `defaultOrganizationId`: Your parent organization ID, which you can find in the [Turnkey dashboard](https://app.turnkey.com/dashboard).
+- `defaultOrganizationId`: Your parent organization ID, which you can find in the [Turnkey dashboard](https://app.turnkey.com/dashboard/v2).
 - `wallet`: The wallet interface used to sign requests. In this example, we'll use the `EthereumWallet` interface.
 
 ```ts config.ts

getting-started/quickstart.mdx

@@ -6,7 +6,7 @@ sidebarTitle: "Account setup"
 
 ## Create an account
 
-Navigate to the [Turnkey Dashboard](https://app.turnkey.com/dashboard/auth/initial) to create an account and setup your organization:
+Navigate to the [Turnkey Dashboard](https://app.turnkey.com/dashboard/v2/auth/initial) to create an account and setup your organization:
 
 <Frame>
   <img src="/images/getting-started/img/quickstart/create_organization.png" />

getting-started/verifiable-cloud-quickstart.mdx

@@ -46,7 +46,7 @@ The public key will be used in the following steps.
 
 <Step title="Create a new TVC app">
 
-Visit the [TVC dashboard](https://app.turnkey.com/dashboard/tvc) and click on "Create app".
+Visit the [TVC dashboard](https://app.turnkey.com/dashboard/v2/tvc) and click on "Create app".
 
 <Frame>
   ![Create app button on the TVC dashboard](/assets/files/tvc_create-app-dashboard.png)
@@ -107,13 +107,13 @@ tvc app create my-app-template.json
 ```
 
 This creates your app, and saves its quorum key and manifest settings to the Turnkey Verifiable Cloud platform.
-Check out your new app on the [TVC dashboard](https://app.turnkey.com/dashboard/tvc).
+Check out your new app on the [TVC dashboard](https://app.turnkey.com/dashboard/v2/tvc).
 </Accordion>
 </Step>
 
 <Step title="Create new TVC deployment">
 
-Once your app is created, click into it on the [dashboard](https://app.turnkey.com/dashboard/tvc). Click on "Create deployment"
+Once your app is created, click into it on the [dashboard](https://app.turnkey.com/dashboard/v2/tvc). Click on "Create deployment"
 to start a new deployment for your app. 
 
 <img src="/assets/files/tvc_create-deployment.png" alt="Create deployment button" width="200"/>
@@ -189,7 +189,7 @@ Deploy to TVC by running
 tvc deploy create deploy-YYYY-MM-DD.json [--pull-secret <path-to-pull-secret>.json]
 ```
 
-Find the newly created deployment by clicking into your app on the [TVC dashboard](https://app.turnkey.com/dashboard/tvc).
+Find the newly created deployment by clicking into your app on the [TVC dashboard](https://app.turnkey.com/dashboard/v2/tvc).
 </Accordion>
 
 </Step>

products/embedded-business-wallets/overview.mdx

@@ -50,7 +50,7 @@ Sponsor gas fees and manage the transaction lifecycle end-to-end from constructi
 
 <Steps>
   <Step title="Set up Turnkey and configure end-user authentication">
-    Create a [Turnkey organization](https://app.turnkey.com/dashboard/auth/initial) and choose which authentication methods to offer your business users. Turnkey supports [passkeys](/authentication/passkeys/introduction), [email OTP](/authentication/email), [phone OTP](/authentication/sms), and [social logins](/authentication/social-logins) out of the box. Enable your preferred methods in the [dashboard](https://app.turnkey.com) or via API. This determines how business users will log in, create sessions, and authorize wallet operations within their sub-organizations.
+    Create a [Turnkey organization](https://app.turnkey.com/dashboard/v2/auth/initial) and choose which authentication methods to offer your business users. Turnkey supports [passkeys](/authentication/passkeys/introduction), [email OTP](/authentication/email), [phone OTP](/authentication/sms), and [social logins](/authentication/social-logins) out of the box. Enable your preferred methods in the [dashboard](https://app.turnkey.com) or via API. This determines how business users will log in, create sessions, and authorize wallet operations within their sub-organizations.
   </Step>
 
   <Step title="Integrate Turnkey into your application using our SDK">

products/key-management/examples/enterprise-disaster-recovery.mdx

@@ -52,7 +52,7 @@ rest, in transit, and during use.
 
 ### 1. Secure Organization Setup and Recovery Policies
 
-Create a [Turnkey organization](https://app.turnkey.com/dashboard/auth/initial) and establish the
+Create a [Turnkey organization](https://app.turnkey.com/dashboard/v2/auth/initial) and establish the
 security foundation for recovery operations:
 
 - Create dedicated recovery users with specific, limited permissions

products/verifiable-cloud/lifecycle.mdx

@@ -6,7 +6,7 @@ This page walks through the full lifecycle of a TVC deployment, from submitting
 
 ## Deployment Setup
 
-Deployments can be done through the [Turnkey dashboard](https://app.turnkey.com/dashboard/tvc) or the [`tvc` CLI](https://crates.io/crates/tvc). To deploy, you provide Turnkey with:
+Deployments can be done through the [Turnkey dashboard](https://app.turnkey.com/dashboard/v2/tvc) or the [`tvc` CLI](https://crates.io/crates/tvc). To deploy, you provide Turnkey with:
 - Your container registry URL (any OCI-compliant registry: GHCR, Docker Hub, ECR, ACR, etc.)
 - The expected executable digest, the SHA256 hash of your binary (the **pivot hash**)
 - The binary path within the container image

sdks/cli.mdx

@@ -6,7 +6,7 @@ sidebarTitle: "CLI"
 
 ## Create your Turnkey organization
 
-- Visit [app.turnkey.com/dashboard/auth/initial](https://app.turnkey.com/dashboard/auth/initial) and enter your email address
+- Visit [app.turnkey.com/dashboard/v2/auth/initial](https://app.turnkey.com/dashboard/v2/auth/initial) and enter your email address
 - Confirm your email by clicking on the link inside of the confirmation email
 - Follow the prompts to add your first authenticator and create your organization
 

sdks/flutter/authentication/social-logins.mdx

@@ -11,7 +11,7 @@ Using OAuth requires configuration in the Turnkey Dashboard and in your app.
 
 ### Enabling OAuth
 
-Navigate to the **Wallet Kit** section in the [Turnkey Dashboard](https://app.turnkey.com/dashboard/walletKit) and enable **OAuth**. If you have not enabled the Auth Proxy, enable it first. See [Getting Started](/sdks/flutter/getting-started) for details.
+Navigate to the **Wallet Kit** section in the [Turnkey Dashboard](https://app.turnkey.com/dashboard/v2/wallet-kit) and enable **OAuth**. If you have not enabled the Auth Proxy, enable it first. See [Getting Started](/sdks/flutter/getting-started) for details.
 
 <img src="/images/sdks/img/enable-oauth.png" alt="OAuth providers configuration" />
 

sdks/kotlin/authentication/social-logins.mdx

@@ -10,7 +10,7 @@ Using OAuth requires a bit of configuration in the Turnkey Dashboard and your ap
 
 ### Enabling OAuth
 
-Navigate to the **Wallet Kit** section in the [Turnkey Dashboard](https://app.turnkey.com/dashboard/walletKit) and enable the
+Navigate to the **Wallet Kit** section in the [Turnkey Dashboard](https://app.turnkey.com/dashboard/v2/wallet-kit) and enable the
 **OAuth**. Note if you have not enabled the Auth Proxy, you will need to do so first. Check out the [Getting Started](/sdks/kotlin/getting-started) guide for more details.
 
 <img

sdks/react-native/authentication/social-logins.mdx

@@ -10,7 +10,7 @@ Using OAuth requires a bit of configuration in the Turnkey Dashboard and your ap
 
 ### Enabling OAuth
 
-Navigate to the **Wallet Kit** section in the [Turnkey Dashboard](https://app.turnkey.com/dashboard/walletKit) and enable the
+Navigate to the **Wallet Kit** section in the [Turnkey Dashboard](https://app.turnkey.com/dashboard/v2/wallet-kit) and enable the
 **OAuth**. Note if you have not enabled the Auth Proxy, you will need to do so first. Check out the [Getting Started](/sdks/react-native/getting-started) guide for more details.
 
 <img

snippets/shared/fiat-on-ramp.mdx

@@ -24,7 +24,7 @@ By embedding Turnkey’s SDK and leveraging our Fiat Onramp you get:
      - Proof of registration and status (e.g. business registration extract; certificate of good standing)
      - Ownership and control structure (e.g. register of shareholders / members; register of directors and officers; ultimate beneficial owner declaration)
      - Identification of directors, beneficial owners (often >10%), and sometimes senior management, including government-issued photo identification, proof of address (e.g. utility bill, bank statement, government letter < 3 months old). Beneficial owners that are entities may need to provide similar documents, as well.
-3. Once your KYB application has been approved, you will be provisioned API Keys. You can then securely upload your provisioned API Keys through turnkey's dashboard [here](https://app.turnkey.com/dashboard/walletKit)
+3. Once your KYB application has been approved, you will be provisioned API Keys. You can then securely upload your provisioned API Keys through turnkey's dashboard [here](https://app.turnkey.com/dashboard/v2/wallet-kit)
 4. You're now ready to start using Turnkey's Fiat Onramp.
 
 ### Onramp Providers