diff --git a/src/data/nav/platform.ts b/src/data/nav/platform.ts
index 8e1df1417d..ea6fe4f7aa 100644
--- a/src/data/nav/platform.ts
+++ b/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',
diff --git a/src/images/content/screenshots/control-api/account-settings-menu-item.png b/src/images/content/screenshots/control-api/account-settings-menu-item.png
deleted file mode 100644
index f770793674..0000000000
Binary files a/src/images/content/screenshots/control-api/account-settings-menu-item.png and /dev/null differ
diff --git a/src/images/content/screenshots/control-api/my-access-tokens-menu-item.png b/src/images/content/screenshots/control-api/my-access-tokens-menu-item.png
deleted file mode 100644
index 76e440c8c8..0000000000
Binary files a/src/images/content/screenshots/control-api/my-access-tokens-menu-item.png and /dev/null differ
diff --git a/src/images/content/screenshots/dash/access-token-set.png b/src/images/content/screenshots/dash/access-token-set.png
new file mode 100644
index 0000000000..4f55a5b8be
Binary files /dev/null and b/src/images/content/screenshots/dash/access-token-set.png differ
diff --git a/src/images/content/screenshots/dash/access-token.png b/src/images/content/screenshots/dash/access-token.png
new file mode 100644
index 0000000000..5ece95e3bc
Binary files /dev/null and b/src/images/content/screenshots/dash/access-token.png differ
diff --git a/src/images/content/screenshots/dash/account.png b/src/images/content/screenshots/dash/account.png
deleted file mode 100644
index 138c5db320..0000000000
Binary files a/src/images/content/screenshots/dash/account.png and /dev/null differ
diff --git a/src/images/content/screenshots/dash/cli.png b/src/images/content/screenshots/dash/cli.png
new file mode 100644
index 0000000000..70d07d4eef
Binary files /dev/null and b/src/images/content/screenshots/dash/cli.png differ
diff --git a/src/images/content/screenshots/dash/create-app.png b/src/images/content/screenshots/dash/create-app.png
deleted file mode 100644
index acb9cea59b..0000000000
Binary files a/src/images/content/screenshots/dash/create-app.png and /dev/null differ
diff --git a/src/images/content/screenshots/dash/dash-tabs.png b/src/images/content/screenshots/dash/dash-tabs.png
deleted file mode 100644
index 48b3a570e2..0000000000
Binary files a/src/images/content/screenshots/dash/dash-tabs.png and /dev/null differ
diff --git a/src/images/content/screenshots/dash/programmatic-man.png b/src/images/content/screenshots/dash/programmatic-man.png
new file mode 100644
index 0000000000..7de103fa7c
Binary files /dev/null and b/src/images/content/screenshots/dash/programmatic-man.png differ
diff --git a/src/images/content/screenshots/dash/stats-chart.png b/src/images/content/screenshots/dash/stats-chart.png
deleted file mode 100644
index ddf94f80d7..0000000000
Binary files a/src/images/content/screenshots/dash/stats-chart.png and /dev/null differ
diff --git a/src/images/content/screenshots/dash/stats-table.png b/src/images/content/screenshots/dash/stats-table.png
deleted file mode 100644
index b1953086cf..0000000000
Binary files a/src/images/content/screenshots/dash/stats-table.png and /dev/null differ
diff --git a/src/images/content/screenshots/dash/your-apps.png b/src/images/content/screenshots/dash/your-apps.png
deleted file mode 100644
index 94576b4fa0..0000000000
Binary files a/src/images/content/screenshots/dash/your-apps.png and /dev/null differ
diff --git a/src/pages/docs/auth/index.mdx b/src/pages/docs/auth/index.mdx
index 88058a1694..ccb7222bad 100644
--- a/src/pages/docs/auth/index.mdx
+++ b/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.
diff --git a/src/pages/docs/channels/options/encryption.mdx b/src/pages/docs/channels/options/encryption.mdx
index 645114aeb5..3886e880f9 100644
--- a/src/pages/docs/channels/options/encryption.mdx
+++ b/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).
diff --git a/src/pages/docs/metadata-stats/metadata/subscribe.mdx b/src/pages/docs/metadata-stats/metadata/subscribe.mdx
index dfddb17ba8..d9e90097bf 100644
--- a/src/pages/docs/metadata-stats/metadata/subscribe.mdx
+++ b/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
-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.
diff --git a/src/pages/docs/platform/account/2fa.mdx b/src/pages/docs/platform/account/2fa.mdx
index 57ee9560f6..8d762a389f 100644
--- a/src/pages/docs/platform/account/2fa.mdx
+++ b/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
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
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
@@ -42,7 +42,7 @@ Disable and re-enable 2FA in order to switch between SMS 2FA and TOTP (time-base
## Enforce 2FA for all users
-[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.
The account owner must already have 2FA enabled for their own login before they can enforce it account-wide.
@@ -50,16 +50,14 @@ The account owner must already have 2FA enabled for their own login before they
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
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.
diff --git a/src/pages/docs/platform/account/app/api.mdx b/src/pages/docs/platform/account/app/api.mdx
deleted file mode 100644
index 611776924c..0000000000
--- a/src/pages/docs/platform/account/app/api.mdx
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: API keys
-meta_description: “Manage Ably API keys by creating, updating, setting restrictions, and exploring integration options.”
-meta_keywords: "API keys, Ably, create key, update key, key restrictions, integration, webhooks, authentication"
-redirect_from:
- - /docs/account/app/api
----
-
-The API keys tab lists all API keys associated with your account and provides information on each key's capabilities and restrictions. You can [create a new API key](#create) and manage an existing one.
-
-
-Before setting up multiple API keys with different permissions or sharing API keys with untrusted parties, consider using [token authentication](/docs/auth/token) instead. Token authentication provides more flexible access control and better security for client-side applications.
-
-
-## Create a new API key
-
-The following steps create a new API Key:
-
-* Click **Create a new API key**.
- * Assign a friendly name.
- * Give the new API key a descriptive name (e.g. chat app key) so it is easy to identify later.
-
-To manage an API key: set [capabilities](/docs/auth/capabilities), define resource restrictions, use revocable tokens for security, and adjust key settings as needed.
-
-### Capabilities
-
-[Capabilities](/docs/auth/capabilities) provide permissions required for managing message flow, user presence, notifications, channel information, and access controls, these depend on what you require the API key to have access to:
-
-| Capability | Description |
-| ---------- | ----------- |
-| **Publish** | Allow clients to publish messages to channels. |
-| **Subscribe** | Allow clients to receive messages and presence state changes. |
-| **History** | Allow clients to retrieve message and presence history. |
-| **Presence** | Allow clients to register presence on a channel. |
-| **Channel metadata** | Allow clients to query channel metadata. |
-| **Push admin and push-subscribe** | Allow clients to manage and subscribe to push notifications. |
-| **Statistics** | Allow clients to query usage statistics. |
-| **Privileged headers** | Allow clients to set privileged headers, such as to skip rules. |
-
-### Set resource restrictions
-
-Set resource restrictions to control access to channels and queues, ranging from unrestricted access to specific, rule-based permissions:
-
-| Restriction | Description |
-| ----------- | ----------- |
-| None | No restrictions; access any channel or queue. |
-| Only channels | Access any channel but not queues. |
-| Only queues | Access any queue but not channels. |
-| Selected channels and queues | Specify explicit rules for access. |
-
-When specifying selected channels and queues, you can provide a comma-separated list of resources. Each resource can match a single channel (e.g., `channel-name`) or multiple channels using wildcards (e.g., `namespace:*`). Queues use the prefix `[queue]` and meta channels use `[meta]`. See [capabilities documentation](/docs/auth/capabilities#wildcards) for detailed wildcard syntax.
-
-
-A single API key cannot support complex permission combinations, such as publish access on one channel and subscribe access on another. For such requirements, use [token authentication](/docs/auth/token) instead.
-
-
-### Revocable tokens
-
-[Revocable tokens](/docs/auth/revocation#revocable-tokens) enhance security by allowing shorter token lifetimes and the ability to revoke tokens issued via the API key.
-
-| Option | Description |
-| ------ | ----------- |
-| Revocable tokens | Implement security measures by setting shorter token lifetimes and enabling the ability to revoke tokens issued by the API key. |
-
-### Change your API key settings
-
-Click **Settings** on the required API key to change its settings. The same settings apply as when creating a new API key.
diff --git a/src/pages/docs/platform/account/app/console.mdx b/src/pages/docs/platform/account/app/console.mdx
deleted file mode 100644
index aec15bb350..0000000000
--- a/src/pages/docs/platform/account/app/console.mdx
+++ /dev/null
@@ -1,79 +0,0 @@
----
-title: Dev console
-meta_description: "Gain realtime insights into application-wide events, such as connection status changes, channel activity, and event logs.”
-meta_keywords: “Ably dev console, realtime monitoring, connection status changes, channel activity, event logs"
-redirect_from:
- - /docs/account/app/console
----
-
-The dev console tab provides realtime insights into application-wide events, such as connection status changes and channel activity. These features enable you to:
-
-* Observe changes in connection status across the application.
-* View activity on specific channels, including message traffic and channel events.
-* Examine event logs to troubleshoot your application.
-
-## Application-wide events interface
-
-The application-wide events interface allows you to monitor your application's health and activity in realtime.
-
-The following explains the realtime monitoring tools in the application-wide events interface:
-
-| Field | Description |
-| ----- | ----------- |
-| **API key** | The API key to access and view events within the app. |
-| **Average application-wide events per second (p/s)** | This metric shows the average number of events occurring per second across your application. For example, if the current rate is 0, no active events are being processed. |
-| **Event log table** | The event log table displays a record of events related to the current client's connection status. This table can be used to debug potential issues in your application. |
-
-## Message auditing and logging
-
-The dev console displays messages in realtime for debugging and testing purposes, but does not provide persistent message auditing or logging capabilities. Ably does not currently offer native functionality to view historical messages filtered by specific channels or client IDs for auditing purposes.
-
-If you need to audit or log messages by channel or client ID, implement this functionality on the application side. Consider using:
-
-- [Webhooks](/docs/platform/integrations/webhooks) to send message events to your logging system
-- [Message queues](/docs/platform/integrations/queues) to process and store message data
-- Client-side logging in your application code
-
-For native message auditing features, [contact support](mailto:support@ably.com) to discuss requirements.
-
-## Channels
-
-The following is a step-by-step instructions for connecting to a channel, publishing messages.
-
-### Connect to a channel
-
-The following explains how to connect to a channel:
-
-| Step | Action |
-| ---- | ------ |
-| **Enter a channel name** | In the channel name field, choose a name (e.g get-started). |
-| **Attach to channel** | Click the **attach to channel** button. This connects you to the **get-started** channel, enabling you to start publishing or subscribing to messages. |
-| **Monitor channel status** | The interface will display the channel status as **pending** and then **attached** once connected, confirming that the channel is ready for interaction.|
-
-### Publish a message
-
-The following explains how to publish a message:
-
-| Step | Action |
-| ---- | ------ |
-| **Message data** | In the **message data** field, type a message (e.g. example). |
-| **Publish message** | Click the **publish message** button to send the message to the **get-started** channel. |
-| **View the message** | If you have a subscriber , it will receive and display the message in the console. |
-
-The following explains how to interact with presence:
-
-| Step | Action |
-| ---- | ------ |
-| **Client ID** | Enter a unique client ID to simulate joining the presence of the channel. |
-| **Enter presence** | Click **enter presence** to indicate that this client is now in the channel. |
-| **Monitor presence** | The interface will list all clients in the channel under **presence members**. |
-
-### Control the channel
-
-The following explains how to control the channel in the dev console:
-
-| Step | Action |
-| ---- | ------ |
-| **Detach** | Click **detach** to disconnect from the channel. |
-| **Pause** | Use **pause** to temporarily stop receiving messages. |
-| **Clear** | Click **clear** to clear the channel data or logs from the interface. |
diff --git a/src/pages/docs/platform/account/app/index.mdx b/src/pages/docs/platform/account/app/index.mdx
deleted file mode 100644
index 28d96d01f6..0000000000
--- a/src/pages/docs/platform/account/app/index.mdx
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: App management overview
-meta_description: " Manage and monitor your applications on the Ably platform using the Ably dashboard. Create new apps, view existing ones, and configure settings from your browser."
-meta_keywords: “Ably dashboard, manage applications, monitor apps, app creation, application settings, Ably platform”
-redirect_from:
- - /docs/account/app
----
-
-Manage and monitor your applications on the Ably platform using the Ably dashboard. Create new apps, view existing ones, and configure settings from your browser.
-
-Begin by [logging](https://ably.com/login) in to Ably through your browser. Once you're logged in, you have access to the Ably [dashboard](https://ably.com/accounts), where you can [create a new app](#create) or [view your existing apps.](#view)
-
-## Create a new app
-
-The following image displays the Ably dashboard when no apps have been created yet. To get started, you can easily **Create new app**:
-
-
-
-## View your apps
-
-If you have created apps already, your dashboard will look similar to the one shown in the following image. Each app displayed is a link to its specific dashboard, where you can view and configure settings, as well as monitor usage and statistics:
-
-
-
-### Environments
-
-Each Ably app acts as a sandboxed environment, isolated from other apps in your account. This makes it straightforward to set up separate environments for development, staging, and production by creating dedicated apps for each.
-
-For example, if you're building a product called "chat-app", you could create:
-
-- `chat-app-production` for your live production environment
-- `chat-app-staging` for pre-production testing
-- `chat-app-development` for ongoing development work
-
-This approach provides complete isolation between environments, ensuring that development activities don't interfere with production traffic. An alternative approach for complete resource isolation, consider using separate Ably accounts for development and production environments. This ensures development activities cannot impact production resources under any circumstances.
-
-
-Account limits are shared. While apps are sandboxed from each other, they share the same [account limits](/docs/platform/pricing/limits) such as connection counts and channel limits. A development app experiencing high usage could potentially impact your production app if account limits are reached.
-
-
-## App overview
-
-Your app dashboard provides the following tabs for monitoring and configuring your app settings:
-
-
-
-### Stats
-
-Monitor and analyze your app's performance through a [stats](/docs/platform/account/app/stats) table and chart:
-
-* Track messages, presence events, and performance metrics to understand usage and capacity.
-* Compare data over time to identify trends and optimize resources.
-* Adjust chart views with zoom options and set specific time ranges for detailed insights.
-
-### Getting started
-
-Get started by connecting to Ably, and publishing your first message.
-
-### API keys
-
-Create, manage, and configure [API keys](/docs/platform/account/app/api) by setting capabilities:
-
-* Users can create a new API key, assigning a descriptive name for easy identification.
-* Capabilities include permissions like publishing messages, subscribing to channels, retrieving message history, managing presence, and accessing statistics.
-* Control access by defining whether the key has unrestricted access, channel-only, queue-only, or specific access to selected channels and queues.
-
-### Integrations
-
-[Integrate](/docs/platform/integrations) Ably with external services, enabling data to flow between Ably channels and third-party platforms:
-
-* Ably events can trigger webhook requests to external services, or external services can send data to Ably using incoming webhooks.
-* Ably enables continuous streaming of events to external services like Amazon Kinesis or Kafka, or can receive inbound streams from external services.
-* Ably supports various integration methods, including HTTP callbacks, cloud functions, and streaming services.
-
-### Queues
-
-View, monitor, and adjust Ably [queues:](/docs/platform/account/app/queues)
-
-* Queues provide access to manage existing queues, monitor data flow, and adjust settings such as TTL, max length, and region.
-* Users can contact Ably support for assistance with increasing limits or customizing their queue settings.
-
-### Notifications
-
-Manage [notifications](/docs/platform/account/app/notifications) using Ably. Create, test, and send notifications to specific devices or channels, and enure everything works correctly.
-
-* Configure push notifications for devices using FCM for Android or APNs for iOS.
-* Use the push inspector tool to test and debug notifications by sending them manually and reviewing device, client, and channel registrations.
-* Use the push inspector widget below to browse and inspect channel subscriptions, device and client registrations.
-
-### Dev console
-
-Monitor your application's health in realtime using Ably's [dev console](/docs/platform/account/app/console) by -- tracking events like connection status changes and channel activity. Connect to channels, publish messages, manage presence, and view event logs for troubleshooting:
-
-* The dev console provides realtime insights into application-wide events like connection status changes, channel activity, and event logs.
-* You can connect to channels, publish messages, and manage presence, tracking interactions within the channel through the console.
-* The event log table displays detailed records of connection events, which can be used for troubleshooting and diagnosing application issues.
-* Interact with Ably channels using command-line tools like cURL.
-
-### Settings
-
-Manage key aspects of your application [settings](/docs/platform/account/app/settings), including security, enabling or disabling the app, configuring rules for channels, and setting up protocol support for different SDKs:
-
-* Manage settings like App ID, name, security (TLS), and enable/disable the application, affecting its ability to accept connections and use Ably services.
-* Create rules to enforce settings for specific channels, or channel namespaces, such as message persistence, TLS-only access, push notifications, and server-side batching.
-* Enable compatibility with various protocols like Pusher, PubNub, and MQTT for communication between client libraries and Ably.
-* Manage notifications for channel activity and occupancy to gain realtime insights into channel usage and performance.
-
diff --git a/src/pages/docs/platform/account/app/notifications.mdx b/src/pages/docs/platform/account/app/notifications.mdx
deleted file mode 100644
index 6e17b52961..0000000000
--- a/src/pages/docs/platform/account/app/notifications.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Notifications
-meta_description: Configure credentials for integrating Ably's push notification services with third-party services, send push notifications from the Ably dashboard, and inspect push notifications .”
-meta_keywords: “Ably push notifications, configure FCM, configure APNs, Web Push setup, push inspector"
-redirect_from:
- - /docs/account/app/notifications
----
-
-Before you can start using Ably's [push notification](/docs/push) services, you must configure the credentials for the third-party services you wish to integrate, such as FCM for Android devices, APNs for iOS devices, or Web Push for web browsers.
-
-### Configure FCM for Android devices
-
-* Go to the [Firebase Console.](https://firebase.google.com/)
-* Click **add project** and follow the steps to **create and manage service account keys**.
-* Download your service account **JSON file**.
-* In your Ably [dashboard](https://ably.com/accounts), navigate to the **notifications** tab under your app settings.
-* Go to **push notifications setup**, click **configure push**.
-* Add your service account **JSON file** to the **setting up Firebase cloud messaging** section.
-
-### Configure APNs for iOS devices
-
-* Go to the [Apple Developer Program.](https://developer.apple.com/programs/)
-* Use the Apple developer portal to create a **push notification** service certificate for your app.
-* Export the certificate as a **.p12 file**.
-* Next, you can either import the **.p12 cert** or create a **PEM file** and copy it into your Ably dashboard:
-
-* Import the **.p12 file**:
- * In your Ably [dashboard](https://ably.com/accounts), navigate to the **Notifications** tab under your app settings.
- * Go to **push notifications setup**, click **configure push** and scroll to the **setting up Apple push notification service** section.
- * Select the **.p12 file** you exported and enter the password you created during the export process.
- * Click **save**. You should receive confirmation that the certificate has been successfully imported.
- * To further confirm the import, refresh the page and check if the **PEM cert** and **private key** text boxes are now populated with the imported key details.
-* Create a **PEM file** from the **.p12 file**:
- * Using [OpenSSL](https://www.openssl.org/), convert the recently exported **.p12 file** (`io.ably.test.p12`) to a **PEM file** with the following command: `$ openssl pkcs12 -in ./io.ably.test.p12 -out ./io.ably.test.pem -nodes -clcerts`.
- * Open the **PEM file** in your text editor.
- * Copy everything between and including `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----`, and paste it into the **PEM cert** text box of the Apple push notification service section of your Ably notifications app [dashboard](https://ably.com/accounts).
- * Similarly, copy everything between and including `-----BEGIN PRIVATE KEY-----` and `-----END PRIVATE KEY-----`, and paste it into the **PEM private key** text box of the same section. Then, click **Save**.
-
-## Push inspector
-
-The Push inspector tool enables you to manually send push notifications by specifying the required data and notification fields. This tool helps test and debug your notification setup before going live.
-
-### API key
-
-The [API Key](/docs/platform/account/app/api) authenticates your requests when sending push notifications. Choose from the list of API keys associated with your Ably account. Each key has different permissions and scopes, so ensure you select the correct one for your notification tasks.
-
-### Push notification title and body
-
-Define the content of your push notification using the fields below:
-
-| Field | Purpose | How to Use |
-| ----- | ------- | ---------- |
-| Notification title | A title for the push notification, which will appear as the headline on the user's device. | Enter a short, clear title that captures the essence of the notification. |
-| Notification body | The main content of the notification to be displayed below the title. | Write the key information or message that you want the user to read. |
-| Notification data | Optional JSON data that the app can use for specific actions upon receiving the notification. | Include any extra data needed for app functionality, such as custom metadata or instructions. |
-
-### Push notification target
-
-Direct your push notifications to specific targets within the Ably platform. Select the appropriate target according to your notification strategy:
-
-| Target | Purpose | How to Use |
-| ------ | ------- | ---------- |
-| Channel name | Push notifications to all subscribers of a specific channel. | Enter the channel name and click push to channel to notify all devices subscribed to that channel. |
-| Device ID | Send a notification directly to a specific device. | Enter the Device ID and click push to device to target a single device with the notification. |
-| Client ID | Notify a specific client registered with Ably. | Enter the Client ID and click push to client to send the notification to the chosen client. |
-
-## Push inspector widget
-
-The Push Inspector widget allows you to monitor and manage your push notification infrastructure directly from the Ably dashboard. It provides insights into channel subscriptions, device registrations, and client registrations, making it easier to debug and optimize your notification setup.
-
-| Section | Purpose | How to Use |
-| ------- | ------- | ---------- |
-| Channel subscriptions | View and inspect all channels currently subscribed to push notifications. | Click inspect channel to see detailed information about a specific channel, including the number of subscribers and recent activity. |
-| Device registrations | Access a list of all devices registered to receive push notifications. | Click inspect device to view detailed information about a specific device, such as its registration status, platform, and recent notifications. |
-| Client registrations | Get an overview of all clients registered for push notifications within the Ably account. | Click inspect client ID to see detailed information about a specific client, including its subscriptions and recent activity. |
diff --git a/src/pages/docs/platform/account/app/queues.mdx b/src/pages/docs/platform/account/app/queues.mdx
deleted file mode 100644
index 4503803ca1..0000000000
--- a/src/pages/docs/platform/account/app/queues.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Queues
-meta_description: Manage and configure Ably queues, monitor realtime data, and optimize performance.”
-meta_keywords: “Ably Queues, realtime data, AMQP, STOMP, queue management, TTL, queue settings"
-redirect_from:
- - /docs/account/app/queues
----
-
-Ably queues provide a way to consume realtime data using the [AMQP](/docs/platform/integrations/queues#consume-amqp) or [STOMP](/docs/platform/integrations/queues#consume-stomp) protocols. Find out more about using [Ably queues](/docs/platform/integrations/queues#what).
-
-## Manage your Ably queues
-
-The Ably queues tab enables you to:
-
-* Access a list of all your existing queues.
-* Monitor realtime data flow and queue performance.
-* Click on any queue to view and adjust its settings, such as TTL, maximum length, and region.
-
-### Provision a new queue
-
-When provisioning a new queue, you'll need to specify several things:
-
-| Field | Description |
-| ----- | ----------- |
-| **Name** | Choose a unique name for your queue. This will help you identify it within your dashboard and during application development. |
-| **Region** | Select the geographic region where the queue will be hosted. This is important for optimizing latency and ensuring data residency aligns with your application's requirements. |
-| **TTL (time to Live)** | Set the TTL, which determines how long messages remain in the queue before being automatically deleted if they are not consumed. The default account limit is 60 minutes. You can contact Ably support for assistance if you need a longer TTL. |
-| **Max length** | Define the maximum number of messages the queue can hold at any given time. The default limit is 10,000 messages, but you can request an increase if your application requires more capacity. |
-
-### Set up queue rules
-
-Once you have provisioned a physical queue, you need to set up one or more queue rules to republish messages, presence events or channel events from pub/sub channels into a queue. Queue rules can either be used to publish to internal queues (hosted by Ably) or external external streams or queues (such as Amazon Kinesis and RabbitMQ). Publishing to external streams or queues is part of our [Ably Firehose servers](/docs/platform/integrations/streaming).
-
-Ably queue rules are setup in the **Integrations** tab found within your app **dashboard**. Find out more about setting up [queue rules](/docs/platform/integrations/queues#setup).
diff --git a/src/pages/docs/platform/account/app/settings.mdx b/src/pages/docs/platform/account/app/settings.mdx
deleted file mode 100644
index ef1dc62212..0000000000
--- a/src/pages/docs/platform/account/app/settings.mdx
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Settings
-meta_description: "Manage your Ably application settings including security, billing, authentication, and protocol support to optimize performance and enhance security."
-meta_keywords: "Ably app settings, application management, security settings, two-factor authentication, billing management, protocol support, channel configuration, push notifications"
-redirect_from:
- - /docs/account/app/settings
----
-
-Manage your Ably application settings including security, billing, authentication, and protocol support to optimize performance and enhance security.
-
-### Application settings overview
-
-The following provides an overview of your application settings.
-
-| Section | Description |
-| ------ | ------------ |
-| **App ID** | This ID is automatically generated by Ably when you create an application. It is a critical part of your application's identity and is included in every API key and token issued for your application. |
-| **Name** | This is the user-defined name that you assigned when creating your application. It is helpful for quickly identifying the application among others in your dashboard, especially if you manage multiple applications. |
-| **Security** | Enabled by default, this option enforces Transport Layer Security (TLS) for all connections to your application. TLS protocol ensures data encryption and secure communication between clients and servers. |
-| **Enabled** | When an application is disabled, it no longer accepts new connections and deactivates all associated services. Clients cannot connect, send or receive messages, or use other Ably services. When enabled, the application allows new connections and activates all related services. |
-
-### Rule configuration
-
-The following explains the configuration rules for specific [namespaces](/docs/channels#namespaces) or [channels](/docs/channels):
-
-| Section | Description |
-| ------- | ----------- |
-| Namespace or channel ID | Identify the specific namespace or channel to which this rule will apply. |
-| Persist last message | Stores the last message published on a channel for 365 days, accessible via the rewind mechanism. |
-| Persist all messages | Ably stores all messages for two minutes by default. Depending on your account package, this can be increased to 24 or 72 hours. It is also possible to persist the last message sent to a channel for a year. |
-| Identified | Requires clients to authenticate with a client ID to interact with channels in this namespace. |
-| TLS only | Restricts access to channels within this namespace to clients connected using TLS. |
-| Push notifications enabled | Enables publishing messages with a push payload, triggering native push notifications to registered devices. |
-| Message interactions enabled | Enables unique time serial fields in messages, enabling typed references between messages (e.g., implementing 'Likes' in a chat). |
-| Server-side batching enabled | Batches inbound messages on the server side before sending them to subscribers based on the configured policy. |
-| Cancel | Discards changes and closes the dialog without saving the new rule.|
-
-### Protocol adapter settings
-
-The following explains the configuration support for various communication protocols ([Pusher](/docs/protocols/pusher), [PubNub](/docs/protocols/pubnub), [MQTT](/docs/protocols/mqtt)), enabling different client libraries to interact with Ably.
-
-| Settings | Description |
-| --------- | ----------- |
-| Pusher protocol support | Provides compatibility with the Pusher protocol. |
-| PubNub protocol support | Provides compatibility with the PubNub protocol. |
-| MQTT protocol support | Provides compatibility with the MQTT protocol. |
-
-### Actions
-
-**Delete this app now** to permanently delete your app including your message history, statistics and prevent access to Ably with any of the API keys assigned to this app.
diff --git a/src/pages/docs/platform/account/app/stats.mdx b/src/pages/docs/platform/account/app/stats.mdx
deleted file mode 100644
index 9387307bd7..0000000000
--- a/src/pages/docs/platform/account/app/stats.mdx
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Stats
-meta_description: “Monitor and analyze your app's performance with Ably's dashboard. Access realtime stats and trends for optimized management."
-meta_keywords: "Ably dashboard, dashboard, app performance, realtime stats, usage monitoring, performance analysis, data trends, statistics chart, statistics table"
-redirect_from:
- - /docs/account/app/stats
----
-
-The stats tab is an interface to monitor your app's performance and usage via the [statistics table](#table) and [statistics chart](#chart).
-
-## Statistics table
-
-The statistics table provides a summary of your app's messaging and data usage patterns over different time frames, including the previous month, the current month, and more granular insights from the last hour and last minute:
-
-
-
-The following explains the statistics table metrics:
-
-| Metric | Description |
-|--------|-------------|
-| Messages (billable) | Total number of messages used. |
-| Messages published (REST & Realtime) | Number of messages sent via REST and Realtime. |
-| Messages received (Realtime) | Number of messages received. |
-| Messages persisted (history) | Number of messages retrieved from history. |
-| Messages retrieved (history) | Number of messages retrieved from history. |
-| Presence events (REST & Realtime) | Number of presence-related events via REST and Realtime. |
-| Webhook / Function | Number of messages transferred through functions and webhooks. |
-| Ably Queue | Number of messages transferred through queues. |
-| Firehose | Number of messages transferred through Firehose. |
-| Push notifications | Number of push notifications sent. |
-| Data transferred | Amount of data transferred, in bytes. |
-| Peak connections | Highest number of concurrent connections. |
-| Peak channels | Highest number of concurrent channels. |
-
-
-Download or view detailed app statistics for a more granular analysis, enabling deeper dives into specific metrics as needed.
-
-
-## Statistics chart
-
-The Stats page also includes a chart that visualizes your app's data over time:
-
-
-
-The following explains how to use the statistics chart:
-
-* **Duration**: Define a specific time range for the statistics you want to view. This enables you to focus on periods of particular interest. For example, set the time range from "2024-06-17 00:00" to "2024-08-06 11:18" to analyze data within that period.
-* **Zoom**: Use preset zoom options (1h, 8h, 24h, 7d, 1m, 6m, 1y, all) to adjust the chart's view to different periods, enabling you to analyze data at various granularities.
diff --git a/src/pages/docs/platform/account/control-api.mdx b/src/pages/docs/platform/account/control-api.mdx
index 8f7ceb42a6..bbf03ab6b3 100644
--- a/src/pages/docs/platform/account/control-api.mdx
+++ b/src/pages/docs/platform/account/control-api.mdx
@@ -11,6 +11,8 @@ redirect_from:
Ably Control API is a REST API that enables you to manage your Ably account programmatically. The Control API also enables you to build web apps and command-line tools, to create and manage your Ably realtime infrastructure. Details of the API can be found in the [Control API Reference](/docs/api/control-api).
+Access your [account dashboard](https://ably.com/accounts/any) to view the apps and resources you can manage with the Control API.
+
Using the Control API you can automate the provisioning, management, and testing of your Ably realtime infrastructure. You can dynamically create Ably apps, configure them, and delete them if necessary. You can implement multi-tenancy solutions for your customers, and create configuration-driven environments that can easily be replicated under programmatic control. Once these environments are created you can also test them using Control API.
With the Control API you can create and manage:
@@ -26,7 +28,7 @@ Repetitive operations such as creating, updating or deleting Ably apps, enumerat
The following diagram illustrates an example use case:
-
+
In this use case, Control API is used to provision a sample app for review and testing purposes. Once provisioned, the [realtime](/docs/api/realtime-sdk) or [REST API](/docs/api/rest-api) can be used to test the app as needed. Once fully tested, the Control API can be used to replicate the app for users as required, using the known-good configuration.
@@ -46,13 +48,11 @@ Using the code-generation capabilities of tools such as [Postman](https://www.po
Before you can use the Control API you must create an access token to authenticate with. You can do this in the Ably dashboard.
-In the [Ably dashboard](https://ably.com/accounts/any), on the top menu bar, select your account from the dropdown list and then select **My Access Tokens** from the menu:
-
-
+In the [Ably dashboard](https://ably.com/accounts/any), select **Personal access tokens** from the user profile dropdown:
You are presented with the **My Access Tokens** area, where you can create tokens for use with the Control API:
-
+
### Creating an access token
@@ -62,7 +62,7 @@ To create a new token, click the **Create new access token** button. Then enter
2. Select the capabilities you wish the token to have, depending on your use case.
3. Click the **Create** button to create the token.
-
+
### Using the access token
@@ -126,13 +126,11 @@ Operations that affect your entire account, such as [listing the apps](/docs/api
### How to find your account ID
-In the [Ably dashboard](https://ably.com/accounts/any), on the top menu bar, select your account from the dropdown list and then select **Account settings**:
-
-
+In the [Ably dashboard](https://ably.com/accounts/any), navigate to the **Settings** section in the sidebar.
Your account settings are displayed. From here you can obtain your Ably account ID, as shown in the following screenshot:
-
+
You'll need your account ID for account-level Control API requests, such as listing all the apps in your Ably account.
@@ -210,12 +208,12 @@ Sample response, with `entries` trimmed for readability:
You can use the Control API to perform tasks such as listing and creating Ably apps. Operations available include:
-* Get a list of apps
-* Create an app
-* Update an app
-* Delete an app
-* Update an app's [APNs](https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/APNSOverview.html) info
-* Retrieve app statistics
+* Get a list of apps.
+* Create an app.
+* Update an app.
+* Delete an app.
+* Update an app's [APNs](https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/APNSOverview.html) info.
+* Retrieve app statistics.
#### Create an app
@@ -342,9 +340,9 @@ Sample response, with `entries` trimmed for readability:
You can use the Control API to manage [Ably queues](/docs/platform/integrations/queues). The main operations are:
-* List all Ably queues
-* Create a queue
-* Delete a queue
+* List all Ably queues.
+* Create a queue.
+* Delete a queue.
#### List queues
@@ -458,10 +456,10 @@ Sample response:
You can use the Control API to manage Ably API keys. The main operations are:
-* List all Ably API keys for an app
-* Create a key
-* Update a key
-* Revoke a key
+* List all Ably API keys for an app.
+* Create a key.
+* Update a key.
+* Revoke a key.
Control API enables you to create a key that has different [capabilities](/docs/auth/capabilities) for different channels.
@@ -615,11 +613,11 @@ In this case there is only a status code returned (200), or an error code.
You can use the Control API to manage Ably [integration rules](/docs/platform/integrations). The main operations are:
-* List all rules for an app
-* List details of a specific rule using rule ID
-* Create a rule
-* Update a rule
-* Delete a rule
+* List all rules for an app.
+* List details of a specific rule using rule ID.
+* Create a rule.
+* Update a rule.
+* Delete a rule.
#### List rules
diff --git a/src/pages/docs/platform/account/enterprise-customization.mdx b/src/pages/docs/platform/account/enterprise-customization.mdx
index 92197df19d..fcc16822dc 100644
--- a/src/pages/docs/platform/account/enterprise-customization.mdx
+++ b/src/pages/docs/platform/account/enterprise-customization.mdx
@@ -9,10 +9,10 @@ redirect_from:
If you're an [Ably Enterprise](https://ably.com/pricing) customer, then you can optionally create a **custom endpoint** to tailor the Ably platform to your specific requirements. A custom endpoint enables you to benefit from the following:
-* **Active traffic management**: Let Ably actively monitor not only the global cluster health but also your own domains and proactively take steps to isolate or move traffic to ensure business continuity.
-* **Dedicated, isolated clusters**: Rely upon guaranteed capacity and isolation from noisy neighbors.
-* **Regional routing of traffic**: Require that all traffic is routed and serviced within specific regions.
-* **Regional message storage**: Require that all messages are stored within a specific region.
+* Active traffic management - Let Ably actively monitor not only the global cluster health but also your own domains and proactively take steps to isolate or move traffic to ensure business continuity.
+* Dedicated, isolated clusters - Rely upon guaranteed capacity and isolation from noisy neighbors.
+* Regional routing of traffic - Require that all traffic is routed and serviced within specific regions.
+* Regional message storage - Require that all messages are stored within a specific region.
A custom endpoint provides you with an option to service Ably platform requests. These can be either subdomains of `ably.net`, or point at your own custom CNAME domain. If you choose the latter option, Ably can also customize our client library SDKs to use your chosen domain and make them available via our CDN as `cdn.ably.com/lib/yourcompany.min.js`.
@@ -38,9 +38,9 @@ We provide you with a custom endpoint for your cluster, for example: `yourcompan
Please note the following:
-* Ably only supports Amazon EC2 environments (within Virtual Private Networks)
-* Ably is responsible for pro-actively managing and updating dedicated clusters
-* Dedicated clusters can run in one or more regions of your choice
+* Ably only supports Amazon EC2 environments (within Virtual Private Networks).
+* Ably is responsible for pro-actively managing and updating dedicated clusters.
+* Dedicated clusters can run in one or more regions of your choice.
If you would like to find out more about our dedicated cluster offering, please [get in touch](https://ably.com/contact).
@@ -65,7 +65,7 @@ This approach does not apply regional restrictions when you are using a persiste
To use a custom endpoint, perform the following steps:
-### Decide whether to use an Ably subdomain, or your own domain
+### Decide whether to use an Ably subdomain, or your own domain
Ably client libraries connect to the `main.realtime.ably.net` domain by default. This domain is used by both WebSocket and other realtime connections from the Ably client libraries, as well as all REST-based requests. It is optimized for all standard HTTP-based request types, including all [REST requests](/docs/api/rest-api), [authentication requests](/docs/auth), and Comet and JSONP fallback when WebSockets cannot be used.
@@ -99,7 +99,7 @@ In addition, Ably handle all certificate renewals, rolling out to our global end
When using your own custom domain, Ably provide these DNS records for you to CNAME to. Although it is recommended that you implement a similar architecture by using CNAMEs under two different domains (for example, `ably.example.com` for your primary traffic and `ably.fallback-example.com` for your fallback traffic, with the latter hosted with a different registrar and using different name servers to the first), this is not mandatory. Therefore, the decision as to whether you need that extra level of redundancy within your own DNS system is yours.
-### Request a custom endpoint
+### Request a custom endpoint
To enable a custom endpoint for your enterprise, speak to your customer success manager. They will create the custom endpoint for you and provide you with a `ClientOptions` object, containing the following options for the `endpoint` property:
@@ -107,7 +107,7 @@ To enable a custom endpoint for your enterprise, speak to your customer success
* `endpoint=main` routes to `main.realtime.ably.net`
* `endpoint=example-eu` routes to `example-eu.realtime.ably.net`
-### Test the custom endpoint
+### Test the custom endpoint
Test your custom endpoint by visiting it. The URL for your endpoint will depend on whether you have opted to use an Ably subdomain or a custom CNAME domain.
@@ -153,7 +153,7 @@ You should then test that all client SDKs can connect, publish, and receive mess
Where possible, you should also inspect your network traffic to verify that the client SDKs are calling the endpoints for your custom endpoint. Instead of connections to `realtime.ably.net` you should see connections to `[ENDPOINT].realtime.ably.net`, or your own custom CNAME domain.
-### Roll out your changes
+### Roll out your changes
Once all your client library SDKs are using the new endpoint and traffic is arriving at the correct endpoints, the team at Ably will be able to actively reroute your traffic based on your endpoint settings.
diff --git a/src/pages/docs/platform/account/index.mdx b/src/pages/docs/platform/account/index.mdx
index 98b7715222..d2486e8bca 100644
--- a/src/pages/docs/platform/account/index.mdx
+++ b/src/pages/docs/platform/account/index.mdx
@@ -1,71 +1,33 @@
---
title: Account overview
-meta_description: "Manage all aspects of your account, from 2FA and billing to user management and personal preferences. "
-meta_keywords: "Ably account, 2FA, billing, user management, personal preferences"
+meta_description: "Overview of the Ably dashboard for managing apps, account settings, team, billing, and usage."
+meta_keywords: "Ably dashboard, account settings, team management, billing, limits, reports"
redirect_from:
- /docs/account
+ - /docs/account/app
+ - /docs/platform/account/app/settings
+ - /docs/account/app/settings
---
-Manage all aspects of your account, from Two-factor authentication ([2FA](/docs/platform/account/2fa)) and billing to user management and personal preferences.
+The [Ably dashboard](https://ably.com/accounts) is where you manage your accounts and apps.
-Begin by [logging](https://ably.com/login) in to Ably through your browser. Once you're logged in, you have access to the Ably dashboard, where you can click on the Account navigation dropdown to access the account settings:
+## Apps
-
+Create a new app to get started with Ably, or select an existing app to configure its settings and monitor connections, channels, and messages that are being used throughout it. You can also view logs and reports for each app to keep on top of your usage and troubleshoot any issues as they arise.
-### Settings
+## Settings
-Manage your Ably account settings, including authentication, [billing](/docs/platform/pricing/billing), and account ownership:
+Manage your Ably account settings, including authentication, billing, and ownership:
* Use your account's unique identifier (Account ID) when contacting support.
-* Account owners can require all users to set up two-factor authentication (2FA) for added security.
-* Account owners and users with the billing role can update billing and package details. They are the only users who can modify these settings or transfer account ownership.
-* Transfer ownership or cancel the account, contact [Ably support.](https://ably.com/support)
+* Account owners can require all users to set up [two-factor authentication (2FA)](/docs/platform/account/2fa) for added security.
+* Update your billing details and package subscription.
+* Transfer ownership or cancel the account.
-### Billing
+## Reports
-Manage your [billing](/docs/platform/pricing/billing) and package settings to scale your services:
+View detailed [reports](https://ably.com/accounts/any/apps/any/reports) about your account and app usage.
-* Review your current package to assess if it fits your needs, whether free, pay-as-you-go, or committed use.
-* Ensure your billing information is up to date, including company name, billing email (optional), address, international phone number, and timezone.
-* View and manage invoices and payment methods once your account has been upgraded.
+## Team
-### Limits
-
-Understand and manage your package [limits](/docs/platform/pricing/limits) by tracking usage across messages, data, connections, and channels:
-
-* Limits are applied to prevent service disruption and vary by package.
-* Limits can be time-based, quantity-based, or rate-based, and they may apply either per connection/channel or across the entire account.
-* Notifications are provided when limits are nearing or exceeded, and detailed logs of warnings and exceeded limits are accessible in the account dashboard.
-
-### Usage
-
-Monitor your account's resource consumption with detailed usage statistics:
-
-* The usage statistics table monitors app performance by tracking resource usage, such as messages, data transferred, connections, and channels.
-* The statistics chart visualizes app usage data over time, allowing users to define specific time ranges, zoom in on different periods, and analyze metrics in detail.
-
-### Users
-
-Manage the [users](/docs/platform/account/users) associated with your account:
-
-* The account owner role has full permissions to manage the account, including inviting and removing users, and assigning roles like developer, billing, or admin.
-* Multiple roles can be assigned to a single user.
-* Remove, or change user roles within an Ably account.
-
-### My Settings
-
-Control personal account settings:
-
-* View and edit name, email, and password.
-* Enable two-factor authentication (2FA) for added security.
-* Connect and manage login providers (Google, GitHub).
-* Customize Ably email preferences (product updates, news, educational emails)
-* Set up notifications for account usage.
-
-### My Access tokens
-
-Create access tokens for the [Control API:](/docs/platform/account/control-api)
-
-* Users can create new tokens by providing a descriptive name, assigning an account, selecting capabilities, and securely storing the token once generated.
-* Users can revoke existing tokens through the settings section, but this action is irreversible and will immediately invalidate the token for API access.
-* After a token is created, the full token cannot be viewed again, so it must be securely stored upon generation.
+[Manage the users](https://ably.com/accounts/any/account_users) that have access to your account. The account owner role has full permissions to manage the account, including adding and removing users, and managing their [roles](/docs/platform/account/team).
diff --git a/src/pages/docs/platform/account/organizations.mdx b/src/pages/docs/platform/account/organizations.mdx
index d71d54dc45..0937991302 100644
--- a/src/pages/docs/platform/account/organizations.mdx
+++ b/src/pages/docs/platform/account/organizations.mdx
@@ -8,6 +8,8 @@ redirect_from:
Use organizations to manage multiple Ably accounts by centralizing user access and roles under a single organizational structure. Organizations streamline user provisioning through [Single Sign-On (SSO)](/docs/platform/account/sso) configuration and utilize SCIM System for Cross-domain Identity Management for group-based access control.
+Access your [organization settings](https://ably.com/accounts/any/organization) to manage your organization configuration and user access.
+
Organizations enable the [primary](#primary) account to assign and adjust the roles of users and groups across all accounts.
You can separate accounts within an organization to create isolated environments, such as production, staging, and development. Assign each environment a [package](/docs/platform/pricing#packages) that meets its specific needs. For example, production may need high capacity with an **Enterprise** package, staging might use a **Standard** package, and development a **Free** package.
@@ -21,17 +23,17 @@ An [Enterprise](/docs/platform/pricing/enterprise) account is required to use or
The primary account is an organization's main account and holds the following privileges:
* The highest level of access to the organization.
-* Ownership of all all accounts within the organization.
+* Ownership of all accounts within the organization.
* The default account used for provisioning.
## Create accounts in an organization
Create accounts in an organization:
-* Open the **Account** navigation dropdown.
- * Click **Organization Accounts.**
- * Click **New account**.
- * Add an account name and **Create account**.
+1. Open the **Account** navigation dropdown.
+2. Click **Organization Accounts**.
+3. Click **New account**.
+4. Add an account name and **Create account**.
## Provision users via SCIM
@@ -47,38 +49,38 @@ Ably only recognizes one registered email domain per organization, unrecognized
Users provisioned through SCIM cannot modify their name or email address within Ably. All personal information updates must be made through your identity provider, and changes will sync to Ably on the next SCIM update cycle.
-The following steps outline the process for provisioning users through SCIM:
-
-* Configure [SSO](/docs/platform/account/sso) by enabling and setting up SSO between Ably and your identity provider.
+Provision users through SCIM:
-* Copy Ably SCIM configuration values:
- * Open the **Account** navigation dropdown in the Ably dashboard.
- * Select **Organization Settings** from the menu.
- * Navigate to the **Users & Groups Provisioning (SCIM)** section and copy:
- * **Service Provider Configuration Endpoint.**
- * **SCIM Username.**
- * **SCIM Password.**
-* In your identity providers provisioning app, paste the following values from Ably:
- * **Service Provider Configuration Endpoint.**
- * **SCIM Username.**
- * **SCIM Password.**
-* Ensure that any additional setup required by your identity provider is completed to finalize the SCIM configuration.
+1. Configure [SSO](/docs/platform/account/sso) by enabling and setting up SSO between Ably and your identity provider.
+2. Copy Ably SCIM configuration values:
+ 1. Open the **Account** navigation dropdown in the Ably dashboard.
+ 2. Select **Organization Settings** from the menu.
+ 3. Navigate to the **Users & Groups Provisioning (SCIM)** section and copy:
+ * **Service Provider Configuration Endpoint**.
+ * **SCIM Username**.
+ * **SCIM Password**.
+3. In your identity providers provisioning app, paste the following values from Ably:
+ * **Service Provider Configuration Endpoint**.
+ * **SCIM Username**.
+ * **SCIM Password**.
+4. Ensure that any additional setup required by your identity provider is completed to finalize the SCIM configuration.
## Manage roles
-Manage user and group [roles](/docs/platform/account/users#roles) across accounts within your organization. User and group roles include those assigned directly to the user and through the groups the user belongs to. Use the **Organization Users** page as a central point of control, rather than managing access individually within each account.
+Manage user and group [roles](/docs/platform/account/team#roles) across accounts within your organization. User and group roles include those assigned directly to the user and through the groups the user belongs to. Use the **Organization Users** page as a central point of control, rather than managing access individually within each account.
### Group roles
When organizations and your identity provider are configured, the groups you create in the identity provider are synchronized with Ably. This enables you to manage group-based access centrally. Assign roles to these groups across one or more accounts. When a group is linked to an account, all users in that group are automatically provisioned into that account and inherit the assigned roles. Users added to the group afterwards are also provisioned into the linked accounts automatically.
-To manage group roles in Ably:
-* Open the **Account** navigation dropdown.
- * Click **Organization Users**.
- * Under **Ably Realtime identity provider groups**, click **Manage account access**.
- * Select the group whose access you want to manage.
- * Specify the required **Roles** for the group -- and all users in this group inherit these roles automatically.
+Manage group roles in Ably:
+
+1. Open the **Account** navigation dropdown.
+2. Click **Organization Users**.
+3. Under **Ably Realtime identity provider groups**, click **Manage account access**.
+4. Select the group whose access you want to manage.
+5. Specify the required **Roles** for the group -- and all users in this group inherit these roles automatically.
When modifying an individual user's roles, any rights assigned via groups will be greyed out and cannot be changed directly.
diff --git a/src/pages/docs/platform/account/sso.mdx b/src/pages/docs/platform/account/sso.mdx
index 31388d71db..861eb8a667 100644
--- a/src/pages/docs/platform/account/sso.mdx
+++ b/src/pages/docs/platform/account/sso.mdx
@@ -10,7 +10,7 @@ Single sign-on (SSO) enables your users to authenticate via any SAML-compatible
## Configure
-Single sign-on is restricted to Enterprise customers only and must be enabled on a per-account basis by [contacting Ably](https://ably.com/support). Only [account owners](/docs/platform/account/users) can configure SSO for an account.
+Single sign-on is restricted to Enterprise customers only and must be enabled on a per-account basis by [contacting Ably](https://ably.com/support). Only [account owners](/docs/platform/account/team) can configure SSO for an account.
Any SAML-compatible identity provider can be used to enable SSO.
@@ -22,10 +22,9 @@ To enable SSO using [Okta](https://www.okta.com/) as the identity provider, conf
In your Ably account dashboard:
-1. Log in to your [account](https://ably.com/accounts/any).
-2. Select **Settings** from the account navigation dropdown.
-3. Toggle **Enable Single Sign-On** under the **Authentication Settings** section.
-4. Note down the **Single sign-on URL** and **Audience URI** values.
+1. Log in to your account and select [Security](https://ably.com/accounts/any/security) in your account.
+2. Toggle **Enable Single Sign-On** under the **Authentication Settings** section.
+3. Note down the **Single sign-on URL** and **Audience URI** values.
In your Okta account:
@@ -40,13 +39,11 @@ Use the [Okta guide](https://developer.okta.com/docs/guides/saml-application-set
In your Ably account dashboard:
-1. Log in to your [account](https://ably.com/accounts/any).
-2. Select **Settings** from the account navigation dropdown.
-3. Complete the SSO fields with the values obtained from Okta:
+1. Complete the SSO fields with the values obtained from Okta:
* Identity Provider Single Sign-On URL
* Identity Provider Issuer
* X.509 Certificate
-4. Save the authentication settings.
+2. Save the authentication settings.
### Google Workspace
@@ -54,10 +51,9 @@ To enable SSO using [Google Workspace](https://workspace.google.com/) as the ide
In your Ably account dashboard:
-1. Log in to your [account](https://ably.com/accounts/any).
-2. Select **Settings** from the account navigation dropdown.
-3. Toggle **Enable Single Sign-On** under the **Authentication Settings** section.
-4. Note down the **Single sign-on URL** and **Audience URI** values.
+1. Log in to your account and select [Security](https://ably.com/accounts/any/security) in your account.
+2. Toggle **Enable Single Sign-On** under the **Authentication Settings** section.
+3. Note down the **Single sign-on URL** and **Audience URI** values.
In your Google Workspace account:
@@ -95,6 +91,5 @@ Account owners can access account resources regardless of their current authenti
To enable strict mode:
-1. Log in to your [account](https://ably.com/accounts/any).
-2. Select **Settings** from the account navigation dropdown.
-3. Toggle **Enable Strict Mode** under the **Authentication Settings** section. This setting is only visible if SSO has been enabled.
+1. Log in to your account and select [Security](https://ably.com/accounts/any/security) in your account.
+2. Toggle **Enable Strict Mode** under the **Authentication Settings** section. This setting is only visible if SSO has been enabled.
diff --git a/src/pages/docs/platform/account/team.mdx b/src/pages/docs/platform/account/team.mdx
new file mode 100644
index 0000000000..83f9aa14a0
--- /dev/null
+++ b/src/pages/docs/platform/account/team.mdx
@@ -0,0 +1,119 @@
+---
+title: Team
+meta_description: "Manage users, roles, and team access in your Ably account."
+meta_keywords: "Ably team, user management, roles, permissions, SSO, SCIM, access management"
+redirect_from:
+ - /docs/platform/account/teams
+ - /docs/platform/account/users
+ - /docs/account/users
+---
+
+Manage who has access to your Ably account and what they can do. Invite users, assign roles, and configure team-based access for Enterprise accounts.
+
+Manage users through your [account dashboard](https://ably.com/accounts/any/users).
+
+## User roles
+
+The user that creates an Ably account is assigned the account owner role. An account can only have a single account owner. Users can be assigned multiple roles:
+
+- Developer
+- Billing
+- Admin
+- Owner
+
+| Permission | Developer | Billing | Admin | Owner |
+|---|---|---|---|---|
+| View all apps | ✓ | ✓ | ✓ | ✓ |
+| View app configuration | ✓ | - | ✓ | ✓ |
+| View app settings | ✓ | - | ✓ | ✓ |
+| View [app statistics](/docs/metadata-stats/stats#app) | ✓ | ✓ | ✓ | ✓ |
+| View [account statistics](/docs/metadata-stats/stats#account) | ✓ | ✓ | ✓ | ✓ |
+| Configure own [2FA](/docs/platform/account/2fa) | ✓ | - | ✓ | ✓ |
+| [Invite new users](#invite) | - | - | ✓ | ✓ |
+| [Remove existing users](#remove) | - | - | ✓ | ✓ |
+| Manage [API keys](/docs/auth) | - | - | ✓ | ✓ |
+| Manage app configuration | - | - | ✓ | ✓ |
+| Manage app settings | - | - | ✓ | ✓ |
+| Create apps | - | - | ✓ | ✓ |
+| Receive [limit notifications](/docs/platform/pricing/limits) | - | - | ✓ | ✓ |
+| Configure [single sign-on](/docs/platform/account/sso) | - | - | - | ✓ |
+| Enforce [2FA](/docs/platform/account/2fa#enforce) | - | - | - | ✓ |
+| View invoices | - | ✓ | - | ✓ |
+| Update billing information | - | ✓ | - | ✓ |
+| Manage [account package](https://ably.com/pricing) | - | - | - | ✓ |
+
+### Change user roles
+
+You must be an account owner or admin to change user roles:
+
+1. Log in to your [account](https://ably.com/accounts/any/users).
+2. Click the checkboxes corresponding to the roles you want to add or remove.
+
+
+Follow [this process](https://faqs.ably.com/can-i-change-my-ably-account-owner) to transfer account ownership.
+
+
+## Invite a new user
+
+You must be an account owner or admin to invite new users:
+
+1. Log in to your [account](https://ably.com/accounts/any/users).
+2. Click "Invite new user".
+3. Enter the user's first name and email address, then click "Invite".
+4. The user can then follow the instructions emailed to them to join your account.
+
+
+You can view the status of pending invitations from the Users page. You can also re-send or revoke an invitation.
+
+
+## Remove users from an account
+
+You must be an account owner or admin to remove users:
+
+1. Log in to your [account](https://ably.com/accounts/any/users).
+2. Click "Remove" next to the user to remove from the account.
+3. Confirm the action when prompted.
+
+## Delete your profile or leave an account
+
+1. Log in to your [account](https://ably.com/accounts/any).
+2. Go to [My Settings](https://ably.com/users/edit).
+3. [Disconnect SSO provider](#sso) if you use SSO to log in.
+4. Scroll to "Want to delete your profile?"
+5. Click "Start" to remove yourself from this account.
+
+
+Account owners: Deleting your profile will delete the entire account and all data. You must first [transfer ownership](https://faqs.ably.com/can-i-change-my-ably-account-owner) to another user before deleting your profile.
+
+
+## Close your account
+
+You must be the account owner and have downgraded to the Free package:
+
+1. Log in to your [Ably account](https://ably.com/accounts/any).
+2. Ensure you are the [account owner](#roles).
+3. [Downgrade your current package](/docs/platform/pricing/free#downgrade) to Free.
+
+
+You will not be able to delete your account until the 1st of the month following your downgrade, after your final invoice has been paid.
+
+
+4. [Disconnect SSO provider](#sso) if you use SSO to log in.
+5. Go to the [Account Settings](https://ably.com/accounts/any/settings) page.
+6. Select **Delete account** and follow the prompts.
+
+
+If you use an SSO login you'll see a "Contact us" link instead of a "Start" button. [Disconnect your SSO provider](#sso) first.
+
+
+### Disconnect SSO provider
+
+If you use SSO to log in, you must set a password and disconnect your SSO provider before closing your account:
+
+1. Log in to your [account](https://ably.com/accounts/any).
+2. Navigate to Account then [My Settings](https://ably.com/users/edit).
+3. In the Password section, click "Change your password".
+4. Click "Update my personal settings" to save the changes.
+5. Scroll to the Login provider section.
+6. Click "remove connection" next to the SSO provider you want to disconnect.
+7. Return to the instructions above to [close your account](#close).
diff --git a/src/pages/docs/platform/account/users.mdx b/src/pages/docs/platform/account/users.mdx
deleted file mode 100644
index ad020cdaba..0000000000
--- a/src/pages/docs/platform/account/users.mdx
+++ /dev/null
@@ -1,127 +0,0 @@
----
-title: User management
-meta_description: "Learn how to manage users, user roles, and the permissions associated with each role."
-meta_keywords: "users, user management, admin, owner, permission"
-redirect_from:
- - /docs/account/users
----
-
-The user that creates an Ably account is assigned the account owner role. An account owner has permission to undertake any action within an account, such as inviting new users. There are two other account roles that inherit a subset of an account owner's permissions. An account can only have a single account owner.
-
-## User roles
-
-Users can be assigned to the following roles. Each user may be assigned multiple roles:
-
-* Developer
-* Billing
-* Admin
-* Owner
-
-User roles have the following permissions:
-
-| Permission | Developer | Billing | Admin | Owner |
-|------------|-----------|---------|-------|-------|
-| View all apps | ✓ | ✓ | ✓ | ✓ |
-| View app configuration | ✓ | - | ✓ | ✓ |
-| View app settings | ✓ | - | ✓ | ✓ |
-| View [app statistics](/docs/metadata-stats/stats#app) | ✓ | ✓ | ✓ | ✓ |
-| View [account statistics](/docs/metadata-stats/stats#account) | ✓ | ✓ | ✓ | ✓ |
-| Configure own [2FA](/docs/platform/account/2fa) | ✓ | - | ✓ | ✓ |
-| [Invite new users](#invite) | - | - | ✓ | ✓ |
-| [Remove existing users](#remove) | - | - | ✓ | ✓ |
-| Manage [API keys](/docs/auth) | - | - | ✓ | ✓ |
-| Manage app configuration | - | - | ✓ | ✓ |
-| Manage app settings | - | - | ✓ | ✓ |
-| Create apps | - | - | ✓ | ✓ |
-| Receive [limit notifications](/docs/platform/pricing/limits) | - | - | ✓ | ✓ |
-| Configure [single sign-on](/docs/platform/account/sso) | - | - | - | ✓ |
-| Enforce [2FA](/docs/platform/account/2fa#enforce) | - | - | - | ✓ |
-| View invoices | - | ✓ | - | ✓ |
-| Update billing information | - | ✓ | - | ✓ |
-| Manage [account package](https://ably.com/pricing) | - | - | - | ✓ |
-
-### Change user roles
-
-The following steps add or remove roles from a user within an Ably account. You must be an account owner or admin to change user roles:
-
-1. Log in to your [account](https://ably.com/accounts/any).
-2. Select Users from the account navigation dropdown.
-3. Click the checkboxes corresponding to the roles you want to add or remove.
-
-
-Follow [this process](https://faqs.ably.com/can-i-change-my-ably-account-owner) to transfer account ownership.
-
-
-## Invite a new user
-
-The following steps invite a new user to your account. You must be an account owner or admin to invite new users:
-
-1. Log in to your [account](https://ably.com/accounts/any).
-2. Select Users from the account navigation dropdown.
-3. Click Invite new user.
-4. Enter the user's first name and email address, then click Invite.
-5. The user can then follow the instructions emailed to them to join your account.
-
-
-You can view the status of pending invitations from the Users page. You can also re-send or revoke an invitation.
-
-
-## Remove users from an account
-
-The following steps remove a user from your account. You must be an account owner or admin to remove users:
-
-1. Log in to your [account](https://ably.com/accounts/any).
-2. Select Users from the account navigation dropdown.
-3. Click the Remove button next to the user to remove from the account.
-4. Confirm the action when prompted.
-
-## Delete your profile or leave an account
-
-The following steps delete your profile or remove yourself from an Ably account:
-
-1. Log in to your [account](https://ably.com/accounts/any).
-2. Go to [My Settings](https://ably.com/users/edit).
-3. [Disconnect SSO provider](#sso) if you use SSO to log in.
-4. Scroll to Want to delete your profile?
-5. Click Start to remove yourself from this account.
-
-
-**Account owners:** Deleting your profile will delete the entire account and all data. You must first [transfer ownership](https://faqs.ably.com/can-i-change-my-ably-account-owner) to another user before deleting your profile.
-
-
-## Close your account
-
-To close your Ably account, you must be the account owner and have downgraded to the Free package. The following steps outline the process to close your account:
-
-1. Log in to your [Ably account](https://ably.com/accounts/any).
-2. Confirm that you are the [account owner](https://ably.com/docs/platform/account/users#roles).
-3. Ensure you are the account [owner](/docs/platform/account/users#roles).
-4. [Downgrade your current package](/docs/platform/pricing/free#downgrade) to Free.
-
-
-You will not be able to delete your account until the 1st of the month following your downgrade, after your final invoice has been paid.
-
-
-5. [Disconnect SSO provider](#sso) if you use SSO to log in.
-6. Go to your [My Settings](https://ably.com/users/edit) page.
-7. Scroll to Want to delete your profile?
-
-
-If you are using an SSO login you'll see a Contact us link instead of a Start button. You'll need to [disconnect your SSO provider](#sso) first.
-
-
-8. Click Start to proceed with permanently closing your account.
-9. On the proceeding Close Your Ably Account page, review the accounts for closure.
-10. Click Close Account to permanently deactivate your account.
-
-### Disconnect SSO provider
-
-If you use SSO (Single Sign-On) to log in to your Ably account, you must first set a password and disconnect your SSO provider before closing your account. The self-service account closure process requires a password to authenticate the closure request. The following steps set a password and disconnect your SSO provider:
-
-1. Log in to your [account](https://ably.com/accounts/any) using your current SSO method (Google or GitHub).
-2. Navigate to Account then [My Settings.](https://ably.com/users/edit)
-3. In the Password section, click Change your password.
-4. Click Update my personal settings to save the changes.
-5. Scroll to the Login provider section.
-6. Click remove connection next to the SSO provider/s you want to disconnect.
-7. After completing these steps, return to the instructions above to [close your account](#close).
diff --git a/src/pages/docs/platform/errors/codes.mdx b/src/pages/docs/platform/errors/codes.mdx
index 4227c886cb..496973e9be 100644
--- a/src/pages/docs/platform/errors/codes.mdx
+++ b/src/pages/docs/platform/errors/codes.mdx
@@ -57,8 +57,8 @@ Resolution: The following steps can help resolve this issue:
* API key initialization:
** Ensure you are the account's **admin** or **owner**.
-** In your [Ably dashboard](https://ably.com/accounts/any) to the **API keys** tab.
-** Use one of these API keys instead of your current one or create a [new API key](/docs/platform/account/app/api#create) with the necessary permissions and privileges and use that to instance the SDK.
+** In your [Ably dashboard](https://ably.com/accounts/any/apps/any/) to the **API keys** tab.
+** Use one of these API keys instead of your current one or create a new API key with the necessary permissions and privileges and use that to instance the SDK.
* Token initialization:
** If you are using [token authentication](/docs/auth/token), ensure you are correctly requesting a valid token before using it with Ably.
@@ -292,14 +292,14 @@ This error occurs when the application has reached the maximum number of [integr
## 40127: Maximum number of keys per application exceeded
-This error occurs when the application has reached the maximum number of [API keys](/docs/platform/account/app/api) set by the [limits](/docs/platform/pricing/limits#app-limits) for your current package.
+This error occurs when the application has reached the maximum number of API keys set by the [limits](/docs/platform/pricing/limits#app-limits) for your current package.
## 40131: Key revoked
This error occurs when the [Ably API key](/docs/auth#api-keys) used to initialize the SDK is no longer valid because it has been [revoked](/docs/auth/revocation) by an admin of the application.
Resolution: The following steps can help resolve this issue:
-* If you are an admin, go to the [API keys tab](/docs/platform/account/app/api) in the Ably dashboard to check for valid keys. Use an existing valid key or create a new one with the necessary permissions.
+* If you are an admin, go to the [API keys tab](https://ably.com/accounts/any/apps/any/app_keys) in the Ably dashboard to check for valid keys. Use an existing valid key or create a new one with the necessary permissions.
* If you are not an admin, request a new API key from an administrator or obtain a token request generated with a valid key.
## 40133: Wrong key; cannot revoke tokens with a different key than the one that issued them
@@ -392,11 +392,11 @@ The following are example for this error:
## 40311: Operation requires TLS connection
-By default, Ably apps require [TLS](/docs/platform/account/app/settings#channel-rule-configuration) for connections. This error occurs when a realtime SDK attempts to connect with TLS disabled (tls: false) while using token authentication.
+By default, Ably apps require TLS for connections. This error occurs when a realtime SDK attempts to connect with TLS disabled (tls: false) while using token authentication.
Resolution: The following steps can help resolve this issue:
* Ensure that the `tls` [`ClientOption`](/docs/api/realtime-sdk?#client-options) is set to true when connecting.
-* If using [API key](/docs/platform/account/app/api#create) authentication, note that this scenario will result in a [`40103`](#40103) error instead.
+* If using API key authentication, note that this scenario will result in a [`40103`](#40103) error instead.
## 40330: Unable to activate account due to placement constraint (unspecified)
diff --git a/src/pages/docs/platform/errors/index.mdx b/src/pages/docs/platform/errors/index.mdx
index cd041ee816..aa972f8cd8 100644
--- a/src/pages/docs/platform/errors/index.mdx
+++ b/src/pages/docs/platform/errors/index.mdx
@@ -3,6 +3,8 @@ title: Debugging
meta_description: "Debugging in Ably supported apps, including troubleshooting techniques, logging options, and tools for error analysis."
redirect_from:
- /docs/errors/
+ - /docs/account/app/console
+ - /docs/platform/account/app/console
---
Errors can occur in various scenarios when using Ably, such as invalid inputs in requests, authentication issues, or connection problems caused by network disruptions. Proper debugging is essential for building a reliable application and troubleshooting.
@@ -212,15 +214,15 @@ The following is an example event published to the `[meta]log` channel as an [`E
```
-## Dev console
+## Web client
-The [Dev console](https://ably.com/accounts/any/apps/any/console) in your Ably dashboard is a quick and easy way to inspect errors. It provides a live stream of all events in your application, which is especially useful during early-stage development or low-traffic periods when events are easier to track:
+The [web client](https://ably.com/accounts/any/apps/any/console) in your Ably dashboard is a quick and easy way to inspect errors. It provides a live stream of all events in your application, which is especially useful during early-stage development or low-traffic periods when events are easier to track:
* Monitor all live events in your application for detailed insights.
* Test publishing and subscribing to channels to identify and resolve issues with these functions.
-The Dev console displays a realtime feed of events. It does not store historical data, so you won't be able to query past events after an error has occurred.
+Note the web client was previously known as the Dev Console.
## Support tickets
diff --git a/src/pages/docs/platform/integrations/queues.mdx b/src/pages/docs/platform/integrations/queues.mdx
index 8750aef3c9..9c34853ffc 100644
--- a/src/pages/docs/platform/integrations/queues.mdx
+++ b/src/pages/docs/platform/integrations/queues.mdx
@@ -8,6 +8,7 @@ redirect_from:
- /docs/general/versions/v0.8/queues
- /docs/general/queues
- /docs/integrations/queues
+ - /docs/account/app/queues
---
Ably Queues are traditional message queues that provide a mechanism for you to consume, process, store or reroute data from Ably to your servers. Queues provide an asynchronous machine-to-machine protocol, with each machine assuming one, or both, roles:
diff --git a/src/pages/docs/platform/pricing/billing.mdx b/src/pages/docs/platform/pricing/billing.mdx
index 19a6f9945a..48b9e18b6f 100644
--- a/src/pages/docs/platform/pricing/billing.mdx
+++ b/src/pages/docs/platform/pricing/billing.mdx
@@ -31,7 +31,7 @@ The following details will appear on your credit card or bank statement when pay
To update your billing details:
-1. Ensure you are the account owner or have the billing [role](/docs/platform/account/users).
+1. Ensure you are the account owner or have the billing [role](/docs/platform/account/team).
2. Log in to your [account](https://ably.com/login) and select *Billing* from the *Account* menu.
You can update your payment details and view your invoices in this screen.
@@ -45,7 +45,7 @@ Billing alerts notify you by email when your monthly spending exceeds a set amou
The following steps guide you through setting up billing alerts:
* Log in to your Ably [account.](https://ably.com/login)
-* In the [Create new alert](https://ably.com/accounts/any/package#billing-alerts-section) section, select the email address from the dropdown list where you want to receive the alert. The available choices depend on your [user role](/docs/platform/account/users#roles).
+* In the [Create new alert](https://ably.com/accounts/any/package#billing-alerts-section) section, select the email address from the dropdown list where you want to receive the alert. The available choices depend on your [user role](/docs/platform/account/team#roles).
* If you are an owner: Yourself and billing users associated with the account.
* If you are a user with a billing role: Yourself only.
* Enter a value greater than your base package fee in the *Amount* field. This amount sets the threshold at which you will receive a notification.
diff --git a/src/pages/docs/platform/pricing/faqs.mdx b/src/pages/docs/platform/pricing/faqs.mdx
index 63c9765d42..dd08b3d1c4 100644
--- a/src/pages/docs/platform/pricing/faqs.mdx
+++ b/src/pages/docs/platform/pricing/faqs.mdx
@@ -152,7 +152,7 @@ Once production-level scale is needed, there's a simple path to upgrade to a sub
Yes.
-1. Ensure you are the [account owner](/docs/platform/account/users).
+1. Ensure you are the [account owner](/docs/platform/account/team).
2. Log in to your [account](https://ably.com/login) and select Billing from the Account menu.
3. Select the package to upgrade or downgrade to.
@@ -160,4 +160,4 @@ Upgrades take effect immediately, whilst downgrades will take effect at the begi
### Can I close my account at any time?
-Yes. You can [close your account](/docs/platform/account/users#close) at any time by downgrading to the Free package.
+Yes. You can [close your account](/docs/platform/account/team#close) at any time by downgrading to the Free package.
diff --git a/src/pages/docs/platform/pricing/free.mdx b/src/pages/docs/platform/pricing/free.mdx
index b685088efe..68a2b74494 100644
--- a/src/pages/docs/platform/pricing/free.mdx
+++ b/src/pages/docs/platform/pricing/free.mdx
@@ -38,7 +38,7 @@ Free package support includes Ably's best effort Service Level Objective (SLO) a
To upgrade your account from a Free package to a Standard or Pro package:
-1. Ensure you are the [account owner](/docs/platform/account/users).
+1. Ensure you are the [account owner](/docs/platform/account/team).
2. Log in to your [account](https://ably.com/login) and select **Billing** from the **Account** menu.
3. Choose the plan you wish to upgrade to and follow the instructions. Upgrades take effect immediately.
@@ -54,7 +54,7 @@ To upgrade your account from a Free package to an [Enterprise package](/docs/pla
To downgrade your account to a Free package:
-1. Ensure you are the [account owner](/docs/platform/account/users).
+1. Ensure you are the [account owner](/docs/platform/account/team).
2. Log in to your [account](https://ably.com/login) and select **Billing** from the **Account** menu.
3. Click the **Downgrade** button.
@@ -62,7 +62,7 @@ If you downgrade to the [Free package](/docs/platform/pricing/free), you will re
## Close your account
-If you're using the Free package, you can [close your account](/docs/platform/account/users#close) at any time.
+If you're using the Free package, you can [close your account](/docs/platform/account/team#close) at any time.
Be aware that this will permanently delete all information associated with your account.
diff --git a/src/pages/docs/platform/pricing/pro.mdx b/src/pages/docs/platform/pricing/pro.mdx
index 7b7ac219c4..57ac03f1d0 100644
--- a/src/pages/docs/platform/pricing/pro.mdx
+++ b/src/pages/docs/platform/pricing/pro.mdx
@@ -39,7 +39,7 @@ Pro package support includes access to Ably support via email with a Service Lev
To upgrade your account from a Free package to a Pro package:
-1. Ensure you are the [account owner](/docs/platform/account/users).
+1. Ensure you are the [account owner](/docs/platform/account/team).
2. Log in to your [account](https://ably.com/login) and select **Billing** from the **Account** menu.
3. Choose the plan you wish to upgrade to and follow the instructions. Upgrades take effect immediately.
@@ -51,7 +51,7 @@ Once you upgrade to a Pro, your usage is counted from that point onwards. For ex
To upgrade your account from a Standard package to a Pro package:
-1. Ensure you are the [account owner](/docs/platform/account/users).
+1. Ensure you are the [account owner](/docs/platform/account/team).
2. Log in to your [account](https://ably.com/login) and select **Billing** from the **Account** menu.
3. Choose the plan you wish to upgrade to and follow the instructions. Upgrades take effect immediately.
@@ -65,7 +65,7 @@ To upgrade your account from a Pro package, [contact us](https://ably.com/contac
To downgrade your account from a Pro package:
-1. Ensure you are the [account owner](/docs/platform/account/users).
+1. Ensure you are the [account owner](/docs/platform/account/team).
2. Log in to your [account](https://ably.com/login) and select **Billing** from the **Account** menu.
3. Click the **Downgrade** button.
@@ -75,7 +75,7 @@ If you downgrade to the [Standard package](/docs/platform/pricing/standard), you
## Close your account
-You can [close your account](/docs/platform/account/users#close) at any time by first downgrading to the Free package.
+You can [close your account](/docs/platform/account/team#close) at any time by first downgrading to the Free package.
Be aware that this will permanently delete all information associated with your account.
diff --git a/src/pages/docs/platform/pricing/standard.mdx b/src/pages/docs/platform/pricing/standard.mdx
index bf90a4b1b8..d9a83ef34f 100644
--- a/src/pages/docs/platform/pricing/standard.mdx
+++ b/src/pages/docs/platform/pricing/standard.mdx
@@ -39,7 +39,7 @@ Standard package support includes access to Ably support via email with a Servic
To upgrade your account from a Free package to a Standard package:
-1. Ensure you are the [account owner](/docs/platform/account/users).
+1. Ensure you are the [account owner](/docs/platform/account/team).
2. Log in to your [account](https://ably.com/login) and select **Billing** from the **Account** menu.
3. Choose the plan you wish to upgrade to and follow the instructions. Upgrades take effect immediately.
@@ -51,7 +51,7 @@ Once you upgrade to a Standard, your usage is counted from that point onwards. F
To upgrade your account from a Standard package to a Pro package:
-1. Ensure you are the [account owner](/docs/platform/account/users).
+1. Ensure you are the [account owner](/docs/platform/account/team).
2. Log in to your [account](https://ably.com/login) and select **Billing** from the **Account** menu.
3. Choose the plan you wish to upgrade to and follow the instructions. Upgrades take effect immediately.
@@ -65,7 +65,7 @@ To upgrade your account from a Standard package to an [Enterprise package](/docs
To downgrade your account from a Standard package to Free:
-1. Ensure you are the [account owner](/docs/platform/account/users).
+1. Ensure you are the [account owner](/docs/platform/account/team).
2. Log in to your [account](https://ably.com/login) and select **Billing** from the **Account** menu.
3. Click the **Downgrade** button.
@@ -73,7 +73,7 @@ If you downgrade to the [Free package](/docs/platform/pricing/free), you will re
## Close your account
-You can [close your account](/docs/platform/account/users#close) at any time by first downgrading to the Free package.
+You can [close your account](/docs/platform/account/team#close) at any time by first downgrading to the Free package.
Be aware that this will permanently delete all information associated with your account.
diff --git a/src/pages/docs/platform/tools/cli.mdx b/src/pages/docs/platform/tools/cli.mdx
index fcd61f7dda..50321ba4af 100644
--- a/src/pages/docs/platform/tools/cli.mdx
+++ b/src/pages/docs/platform/tools/cli.mdx
@@ -8,7 +8,9 @@ meta_keywords: "Ably CLI, command line, terminal, developer tools"
The [Ably CLI](https://github.com/ably/ably-cli) is currently in Public Preview status.
-The Ably CLI brings the full power of Ably to your terminal. You can use it to manage your Ably account and its resources, and to explore Ably's APIs and features.
+The Ably CLI brings the full power of Ably to your terminal. You can use it to manage your Ably account and its resources, and to explore Ably's APIs and features. The same capabilities are also available in the CLI section of the [Ably dashboard](https://ably.com/accounts/any/apps/any/).
+
+
It's a quick and easy way to simulate additional clients when testing how Ably works.
diff --git a/src/pages/docs/push/index.mdx b/src/pages/docs/push/index.mdx
index 149cad093e..11d7950c22 100644
--- a/src/pages/docs/push/index.mdx
+++ b/src/pages/docs/push/index.mdx
@@ -13,6 +13,8 @@ redirect_from:
- /docs/general/push-notifications
- /docs/general/versions/v0.8/push-notifications
- /docs/general/smart-notifications
+ - /docs/account/app/notifications
+ - /docs/platform/account/app/notifications
---
Push notifications notify user devices or browsers regardless of whether an application is open and running. They deliver information, such as app updates, social media alerts, or promotional offers, directly to the user's screen. Ably sends push notifications to devices using [Firebase Cloud Messaging](https://firebase.google.com/docs/cloud-messaging) or [Apple Push Notification Service](https://developer.apple.com/notifications/), and to browsers using [Web Push](https://developer.mozilla.org/en-US/docs/Web/API/Push_API). Push notifications don't require a device or browser to stay connected to Ably. Instead, a device's or browser's operating system or web browser maintains its own battery-efficient transport to receive notifications.