[DX-444] Update account and app docs

src/data/nav/platform.ts

@@ -272,8 +272,8 @@ export default {
           index: true,
         },
         {
-          name: 'User management',
-          link: '/docs/platform/account/users',
+          name: 'Team',
+          link: '/docs/platform/account/team',
         },
         {
           name: 'Organizations',
@@ -291,40 +291,6 @@ export default {
           name: 'Enterprise customization',
           link: '/docs/platform/account/enterprise-customization',
         },
-        {
-          name: 'App management',
-          pages: [
-            {
-              name: 'Overview',
-              link: '/docs/platform/account/app',
-              index: true,
-            },
-            {
-              name: 'Stats',
-              link: '/docs/platform/account/app/stats',
-            },
-            {
-              name: 'API keys',
-              link: '/docs/platform/account/app/api',
-            },
-            {
-              name: 'Queues',
-              link: '/docs/platform/account/app/queues',
-            },
-            {
-              name: 'Notifications',
-              link: '/docs/platform/account/app/notifications',
-            },
-            {
-              name: 'Dev console',
-              link: '/docs/platform/account/app/console',
-            },
-            {
-              name: 'Settings',
-              link: '/docs/platform/account/app/settings',
-            },
-          ],
-        },
         {
           name: 'Programmatic management using Control API',
           link: '/docs/platform/account/control-api',

src/pages/docs/auth/index.mdx

@@ -18,6 +18,8 @@ redirect_from:
   - /docs/general/authentication
   - /docs/general/_authentication_capabilities
   - /docs/ids-and-keys
+  - /docs/account/app/api
+  - /docs/platform/account/app/api
 ---
 
 All interactions between a client and the Ably service must be authenticated.

src/pages/docs/channels/options/encryption.mdx

@@ -32,7 +32,7 @@ Unencrypted communication with Ably is **disallowed** if any of the following co
 
 * You attempt to use [Basic Authentication](/docs/auth/basic) and thus transmit a private API key over an unencrypted connection. You are only permitted to use unencrypted connections with [Token Authentication](/docs/auth/token) as tokens expire, limiting the impact of token interception.
 
-* You have specified that TLS is required in your [app settings](/docs/platform/account/app/settings).
+* You have specified that TLS is required in your [app settings](https://ably.com/accounts/any/apps/any/edit).
 
 * A client using an unencrypted connection attempts to attach to a channel that is configured to be used with [TLS only](/docs/channels#rules).
 

src/pages/docs/metadata-stats/metadata/subscribe.mdx

@@ -58,7 +58,7 @@ The `data` property of all events is a [`ChannelDetails`](/docs/api/realtime-sdk
 
 ### Regional channel activity <a id="regional-activity"/>
 
-Seeing `channel.region.inactive` events in your [Dev Console](/docs/platform/account/app/console) logs is normal behavior. Channels become active in different regions globally according to where clients are located and Ably's internal placement rules.
+Seeing `channel.region.inactive` events in your [Web Client](https://ably.com/accounts/any/apps/any/console) logs is normal behavior. Channels become active in different regions globally according to where clients are located and Ably's internal placement rules.
 
 A `channel.region.inactive` event indicates that a channel no longer has any clients in that specific region, or that the channel is shutting down altogether. This is part of Ably's normal operation to efficiently manage resources across its global infrastructure.
 

src/pages/docs/platform/account/2fa.mdx

@@ -8,28 +8,28 @@ redirect_from:
 
 Two-factor authentication (2FA) is an authentication process requiring users to utilize two different forms of verification. 2FA for your Ably account requires your password and a security token sent to your mobile phone.
 
+Access your [account settings](https://ably.com/accounts/any/user/edit) to configure two-factor authentication for your Ably account.
+
 ## Enable 2FA <a id="enable"/>
 
 To enable 2FA for your own user login:
 
-1. Log in to your [account](https://ably.com/accounts/any).
-2. Select **My Settings** from the account navigation dropdown.
-3. Toggle **Enable Two-Factor Authentication** under the **Two-factor authentication** section.
+1. Log in to your account and select [Profile Settings](https://ably.com/users/edit) in your account.
+2. Toggle **Enable Two-Factor Authentication** under the **Two-factor authentication** section.
     * Re-enter your password as prompted.
-4. Select your **Country**.
-5. Enter your **Phone number**
-6. Click **Next** to receive an SMS with a security token.
-7. Enter the security token and click **Verify security code**.
-8. Scan the QR code into an authenticator app such as Authy, or Google Authenticator.
-9. Store your recovery codes in a safe location.
+3. Select your **Country**.
+4. Enter your **Phone number**
+5. Click **Next** to receive an SMS with a security token.
+6. Enter the security token and click **Verify security code**.
+7. Scan the QR code into an authenticator app such as Authy, or Google Authenticator.
+8. Store your recovery codes in a safe location.
 
 ### Disable 2FA <a id="disable"/>
 
 To disable 2FA for your own user login:
 
-1. Log in to your [account](https://ably.com/accounts/any).
-2. Select **My Settings** from the account navigation dropdown.
-3. Click the **Disable Two-Factor Authentication** button.
+1. Log in to your account and select [Profile Settings](https://ably.com/users/edit) in your account.
+2. Click the **Disable Two-Factor Authentication** button.
     * Re-enter your password as prompted.
 
 ### Change phone number <a id="phone"/>
@@ -42,24 +42,22 @@ Disable and re-enable 2FA in order to switch between SMS 2FA and TOTP (time-base
 
 ## Enforce 2FA for all users <a id="enforce"/>
 
-[Account owners](/docs/platform/account/users) can require 2FA to be utilized by all users. Any user that hasn't already enabled 2FA will be prompted to do so the next time they attempt to access the account.
+[Account owners](/docs/platform/account/team) can require 2FA to be utilized by all users. Any user that hasn't already enabled 2FA will be prompted to do so the next time they attempt to access the account.
 
 <Aside data-type='note'>
 The account owner must already have 2FA enabled for their own login before they can enforce it account-wide.
 </Aside>
 
 To enforce 2FA for all users:
 
-1. Log in to your [account](https://ably.com/accounts/any).
-2. Select **Settings** from the account navigation dropdown.
-3. Toggle **Require Two-Factor Authentication for all account users** under the **Authentication Settings** section.
-4. **Save** the authentication settings.
+1. Log in to your account and select [Profile Settings](https://ably.com/users/edit) in your account.
+2. Toggle **Require Two-Factor Authentication for all account users** under the **Authentication Settings** section.
+3. **Save** the authentication settings.
 
 ### Remove 2FA requirement of all users <a id="remove"/>
 
 To remove the requirement for all users to authenticate with 2FA:
 
-1. Log in to your [account](https://ably.com/accounts/any).
-2. Select **Settings** from the account navigation dropdown.
-3. Toggle **Require Two-Factor Authentication for all account users** under the **Authentication Settings** section.
-4. **Save** the authentication settings.
+1. Log in to your account and select [Profile Settings](https://ably.com/users/edit) in your account.
+2. Toggle **Require Two-Factor Authentication for all account users** under the **Authentication Settings** section.
+3. **Save** the authentication settings.