fixup! Update dashboard documentation with new images and improved structure

Author: GregHolmes

src/pages/docs/platform/account/app/configuration/api-keys.mdx

@@ -27,7 +27,7 @@ To manage an API key: set [capabilities](/docs/auth/capabilities), define resour
 
 ### Capabilities <a id="capabilities"/>
 
-[Capabilities](/docs/auth/capabilities) define what permissions your API key has. You can select from core messaging capabilities (subscribe, publish, presence), content management (message updates/deletes, annotations), data access (history, stats), push notifications, and administrative features. See the [capabilities documentation](/docs/auth/capabilities) for the complete list and detailed descriptions.
+[Capabilities](/docs/auth/capabilities) define what permissions your API key has. You can select from core messaging capabilities (subscribe, publish, presence), content management (message updates/deletes, annotations), data access (history, stats), push notifications, and administrative features.
 
 ### Set resource restrictions <a id="resource-restrictions"/>
 

src/pages/docs/platform/account/app/configuration/integrations.mdx

@@ -7,17 +7,17 @@ redirect_from:
   - /docs/account/app/integrations
 ---
 
-The Integrations section in your Ably dashboard provides centralized management for connecting your Ably application with external services and systems. Configure and manage your integrations in the [app dashboard](https://ably.com/accounts/any/apps/any/integrations).
+The Integrations section allows you to connect your Ably application with external services and systems. Configure and manage your integrations in the [app dashboard](https://ably.com/accounts/any/apps/any/integrations).
 
-![Integration dashboard interface](../../../../../../images/content/screenshots/dash/integration.png)
+![Integration management interface](../../../../../../images/content/screenshots/dash/integration.png)
 
 ## Available integration types <a id="available-integrations"/>
 
-The Integrations dashboard allows you to configure several types of integrations:
+You can configure the following types of integrations:
 
-- [Webhooks](/docs/platform/integrations/webhooks) - Trigger serverless functions or custom servers on Ably events
-- [Ably Queues](/docs/platform/integrations/queues) - Scalable realtime data consumption for message processing
-- [Firehose](/docs/platform/integrations/streaming) - Stream data to external systems like Kinesis or Kafka
+- [Inbound webhooks](/docs/platform/integrations/webhooks#inbound) - Receive events from external services into Ably
+- [Outbound webhooks](/docs/platform/integrations/webhooks) - Trigger serverless functions or custom servers on Ably events
+- [Outbound streaming](/docs/platform/integrations/streaming) - Stream data to external systems like Kinesis or Kafka
 - [Third-party integrations](/docs/platform/integrations) - Connect with external services like Datadog
 
 <Aside data-type='note'>

src/pages/docs/platform/account/app/configuration/rules.mdx

@@ -7,7 +7,7 @@ redirect_from:
   - /docs/account/app/rules
 ---
 
-The rules section in your Ably dashboard enables you to enforce settings and configure features for channels, rooms, or spaces within specified namespaces. Configure and manage your rules in the [app dashboard](https://ably.com/accounts/any/apps/any/rules) under the rules section. Rules provide granular control over message persistence, authentication requirements, security settings, and advanced functionality across your application.
+Rules allow you to configure features for channels, rooms, or spaces within specified namespaces. Configure and manage your rules in the [app dashboard](https://ably.com/accounts/any/apps/any/rules). Rules control message persistence, authentication requirements, security settings, and other functionality.
 
 ![Rules dashboard screenshot](../../../../../../images/content/screenshots/dash/rules.png)
 
@@ -31,26 +31,34 @@ The Rules system provides access to multiple feature categories that can be enab
 
 ### Message persistence features <a id="persistence-features"/>
 
+Control how messages are stored for channels in this namespace:
+
 | Feature | Description |
 |---|---|
 | Persist last message | Store the most recent message published to channels. |
 | Persist all messages | Store all messages published to channels. |
 
 ### Security and access features <a id="security-features"/>
 
+Enforce security requirements for channels in this namespace:
+
 | Feature | Description |
 |---|---|
 | Identified | Require client identification for channel access. |
 | TLS only | Enforce encrypted connections for channel access. |
 
 ### Push notification features <a id="push-features"/>
 
+Configure push notification delivery for channels in this namespace:
+
 | Feature | Description |
 |---|---|
 | Push notifications | Enable push notification delivery. |
 
 ### Message processing features <a id="processing-features"/>
 
+Configure message processing behavior for channels in this namespace:
+
 | Feature | Description |
 |---|---|
 | Message interactions | Enable message references and threading. |

src/pages/docs/platform/account/app/configuration/settings.mdx

@@ -7,16 +7,16 @@ redirect_from:
   - /docs/account/app/settings
 ---
 
-The Settings section in your Ably dashboard provides centralized configuration management for your application's core settings, security requirements, and protocol support. Configure your application settings in the [app dashboard](https://ably.com/accounts/any/apps/any/settings) under the Settings section. This interface enables you to customize your application's behavior, enforce security policies, and enable protocol adapters for different client types.
+The Settings section allows you to configure your application's core settings, security requirements, and protocol support. Configure your application settings in the [app dashboard](https://ably.com/accounts/any/apps/any/settings).
 
 ![App settings interface](../../../../../../images/content/screenshots/dash/app-settings.png)
 
 ## Application settings <a id="application-settings"/>
 
-The application settings section contains the fundamental configuration options that define your application's identity and basic operational parameters.
-
 ### Basic application configuration <a id="basic-configuration"/>
 
+The following settings define your application's identity:
+
 | Setting | Description |
 |---|---|
 | App ID | Unique identifier for your application. |
@@ -36,7 +36,7 @@ When TLS required is enabled, this setting overrides any channel settings and en
 
 ### Application status <a id="application-status"/>
 
-Control whether your application accepts new connections and processes requests:
+Control whether your application accepts connections and processes requests:
 
 | Status setting | Description |
 |---|---|
@@ -45,13 +45,7 @@ Control whether your application accepts new connections and processes requests:
 
 ## Protocol Adapter Settings <a id="protocol-adapter-settings"/>
 
-The Ably platform offers protocol adapter services that enable client libraries for different protocols to communicate directly with Ably, extending compatibility beyond native Ably SDKs.
-
-### Protocol adapter overview <a id="protocol-adapter-overview"/>
-
-Protocol adapters allow clients using standard messaging protocols to connect to your Ably application without requiring Ably-specific client libraries. This enables integration with existing systems and tools that support these protocols.
-
-### Available protocol adapters <a id="available-adapters"/>
+Protocol adapters allow clients using standard messaging protocols to connect to your Ably application without requiring Ably-specific client libraries:
 
 | Protocol | Description |
 |---|---|

src/pages/docs/platform/account/app/monitoring/logs.mdx

@@ -7,101 +7,40 @@ redirect_from:
   - /docs/account/app/logs
 ---
 
-The Logs section in your Ably dashboard provides comprehensive monitoring and debugging capabilities through detailed historical event logging across all aspects of your application. Access your application logs in the [app dashboard](https://ably.com/accounts/any/apps/any/logs) under the Logs section. These are historical logs with a short delay, not live logs. This interface enables you to track system activities, troubleshoot issues, and analyze patterns across API requests, channels, connections, integrations, and push notifications.
+The Logs section provides historical event logging for monitoring and debugging your application. Access your application logs in the [app dashboard](https://ably.com/accounts/any/apps/any/logs). Logs are recorded with a short delay.
 
 ![API requests logs interface](../../../../../../images/content/screenshots/dash/log1.png)
 
-## Log sections overview <a id="sections-overview"/>
+## Log sections <a id="sections-overview"/>
 
-The logs interface is organized into five specialized sections, each focused on different aspects of your Ably implementation:
+The logs interface is organized into the following sections:
 
 | Log section | Description |
 |---|---|
-| API requests | Monitor REST API calls and authentication attempts |
-| Channels | Track channel events and activities |
-| Connections | Monitor client connection events |
-| Integration errors | Track integration failures and webhook issues |
-| Push notifications | Monitor push notification delivery and errors |
-| API integrations | Monitor third-party API integration events and errors |
+| API requests | REST API calls and authentication attempts |
+| Channels | Channel events and activities |
+| Connections | Client connection events |
+| Integration errors | Integration failures and webhook issues |
+| Push notifications | Push notification delivery and errors |
 
-Each section provides date range filtering and specialized search capabilities tailored to the specific type of events being monitored.
+Each section provides date range filtering and search capabilities for the specific type of events being monitored.
 
 ## API requests <a id="api-requests"/>
 
-The API requests section provides detailed logs of REST API calls, authentication attempts, and system operations for monitoring and troubleshooting API usage.
-
-### API request filtering options <a id="api-filtering"/>
-
-Filter your API request logs to find specific events:
-
-| Filter | Description |
-|---|---|
-| Date range | Select start and end dates to focus on specific timeframes. |
-| Log level | Choose specific log levels to focus on errors or informational events. |
-| Event name | Enter event names to find particular API operations. |
-| Operation | Search for specific REST operations like GET, POST, PUT, DELETE. |
-| Path | Enter API paths to track specific endpoint usage. |
-| Channel | Enter channel names to see API requests affecting specific channels. |
-| Client ID | Track API requests from specific clients. |
-| Ably Error code | Enter error codes to investigate specific failure types. |
-| API Key ID | Track API usage by specific API keys. |
+The API requests section logs REST API calls, authentication attempts, and system operations. You can filter by date range, log level, event name, operation, path, channel, client ID, error code, and API key ID.
 
 ## Channels <a id="channels"/>
 
-The channels section provides detailed logs of channel events and activities, enabling you to monitor channel lifecycle, message flow, and channel-specific operations.
-
-### Channel log filtering options <a id="channel-filtering"/>
-
-Filter your channel logs to analyze specific events:
-
-1. Select dates to focus on specific channel activity periods.
-2. Filter by specific levels to focus on channel errors or events.
-3. Type event names like channel.attached, channel.detached.
-4. Enter channel names to monitor specific channel activities.
-5. Toggle to include or exclude metadata channels in results.
-6. Enter Ably error codes to investigate channel-specific issues.
+The channels section logs channel events and activities. You can filter by date range, log level, event name, channel name, and error code. You can also toggle metadata channel inclusion.
 
 ## Connections <a id="connections"/>
 
-The connections section provides detailed logs of client connection events, helping you troubleshoot connection issues and monitor client behavior patterns.
-
-### Connection log filtering options <a id="connection-filtering"/>
-
-Filter your connection logs to analyze events and client behavior:
-
-1. Select dates to focus on specific connection activity periods.
-2. Filter by specific levels to focus on connection errors or state changes.
-3. Type events like connection.connected, connection.disconnected.
-4. Monitor events for individual client connections using the connection ID filter.
-5. Monitor connection events for specific application clients using the client ID filter.
-6. Analyze connection patterns by region or investigate regional issues using the country filter.
-7. Search for WebSocket, HTTP, or other transport-specific events using the transport filter.
-8. Enter Ably error codes to investigate connection failures.
-9. Track connection events by API key usage.
+The connections section logs client connection events. You can filter by date range, log level, event name, connection ID, client ID, country, transport type, error code, and API key ID.
 
 ## Integration errors <a id="integration-errors"/>
 
-The integration errors section provides detailed logs of integration failures, webhook issues, and external service connectivity problems.
-
-### Integration error filtering options <a id="integration-filtering"/>
-
-Filter your integration error logs to troubleshoot issues:
-
-1. Select dates to focus on specific integration activity periods.
-2. Select specific integrations like webhooks, queues, or streaming services.
-3. Track events for individual integration configurations using the integration ID filter.
-4. Enter channel names to see integration events from specific channels.
-5. Enter error codes to investigate integration failure types.
+The integration errors section logs integration failures and webhook issues. You can filter by date range, integration type, integration ID, channel, and error code.
 
 ## Push notifications <a id="push-notifications"/>
 
-The push notifications section provides detailed logs of push notification events, delivery status, and related errors for troubleshooting notification delivery issues.
-
-### Push notification filtering options <a id="push-filtering"/>
-
-Filter your push notification logs to analyze delivery and troubleshoot issues:
-
-1. Select dates to focus on specific notification delivery periods.
-2. Enter channel names to track notifications from specific channels.
-3. Enter Ably error codes to investigate notification delivery failures.
-
+The push notifications section logs push notification delivery events and errors. You can filter by date range, channel, and error code.

src/pages/docs/platform/account/app/monitoring/reports.mdx

@@ -7,60 +7,22 @@ redirect_from:
   - /docs/account/app/reports
 ---
 
-The Reports section in your Ably dashboard provides comprehensive analytics and insights for your application, enabling you to monitor usage patterns, analyze costs, and optimize your implementation. View your application reports in the [app dashboard](https://ably.com/accounts/any/apps/any/reports) under the Reports section. This interface offers both high-level summaries and detailed breakdowns of your application's activity.
+The Reports section provides analytics and usage insights for your application. View your application reports in the [app dashboard](https://ably.com/accounts/any/apps/any/reports).
 
-### Available report sections <a id="available-sections"/>
-
-Currently available reports:
-
-| Report | Description |
-|---|---|
-| Global usage report | Comprehensive usage metrics and cost analysis for your application |
+<Aside data-type='note'>
+Reports are available at different levels: organization, account, and app. The scope of the data depends on which level you are viewing.
+</Aside>
 
 ## Global usage report <a id="global-usage"/>
 
-### Billable consumption reports <a id="billable-consumption"/>
-
-The billable consumption section provides detailed usage metrics and cost analysis through the Global usage report.
-
-#### Global usage report <a id="global-usage-detail"/>
-
-The Global usage report offers a consolidated view of your application's realtime activity and efficiency, showing:
-
-- Growth trends and traffic patterns
-- Resource consumption breakdowns
-- Billable usage patterns and optimization opportunities
-
-Click on the Global usage report to access detailed consumption analytics and usage breakdowns.
-
-## Global usage detailed view <a id="global-usage-detailed"/>
-
-When you access the Global usage report, you see comprehensive analytics across multiple categories that help you understand your application's resource consumption and identify optimization opportunities.
-
-### Billable messages <a id="billable-messages"/>
+The Global usage report provides a consolidated view of your application's realtime activity, including:
 
-The billable messages section tracks message traffic across delivery methods including inbound/outbound realtime and REST messages, persisted messages, integrations, push notifications, and optimization savings. The total messages chart displays volume trends over time.
-
-### Billable connections <a id="billable-connections"/>
-
-Connection analytics track your application's client connectivity patterns including connection minutes and peak concurrent connections to help you understand connection patterns and plan for scaling requirements.
-
-### Billable channels <a id="billable-channels"/>
-
-Channel usage metrics provide insights into your messaging infrastructure utilization including channel minutes and peak concurrent channels to help you monitor channel scaling patterns.
-
-### Message type traffic <a id="message-type-traffic"/>
-
-This section breaks down message activity by content type including messages, presence events, objects, and annotations.
-
-### Cost optimization insights <a id="cost-optimization"/>
-
-The reports include analysis of Ably's built-in optimization features that reduce your costs including delta bandwidth savings and batching/conflation savings that eliminate unnecessary messages.
+- Billable messages across delivery methods (realtime, REST, persisted, integrations, push notifications)
+- Connection analytics (connection minutes, peak concurrent connections)
+- Channel usage metrics (channel minutes, peak concurrent channels)
+- Message type traffic breakdown (messages, presence events, objects, annotations)
+- Cost optimization insights (delta bandwidth savings, batching/conflation savings)
 
 ### Usage breakdown <a id="usage-breakdown"/>
 
-The detailed usage breakdown provides granular analysis with comprehensive hourly data tables showing metrics such as messages, bandwidth, connections, channels, and push notifications. This tabular data enables detailed analysis of usage patterns and helps identify opportunities for further optimization.
-
-#### Export functionality <a id="export-functionality"/>
-
-The usage breakdown data can be exported as a CSV file for further analysis in external tools. CSV exports are automatically named with timestamps (for example, `app_stats_details_v2_0_1_2025-12-29T19_09_45.352702118Z.csv`) to help you organize and track different export versions.
+The detailed usage breakdown provides hourly data tables showing metrics such as messages, bandwidth, connections, channels, and push notifications. This data can be exported as a CSV file for further analysis.