RDoc-4056 - agents view documented in /dashboard/manage-an-app/app-agents-view

quill/channels/discord-bot.mdx

@@ -216,7 +216,7 @@ The new channel appears in the **Channels** section:
 2. **Status**  
    **Active**: the channel is enabled; **Disabled**: the channel is paused.  
    Pausing and resuming a channel is described in
-   [Dashboard: Channels view](../dashboard/channels-view.mdx#pausing-and-resuming-a-channel).
+   [App: Channels view](../dashboard/manage-an-app/channels-view.mdx#pausing-and-resuming-a-channel).
 3. **Active links**  
    Embed links belong to web widget channels; a Discord bot channel has none, so the column shows a dash.
 
@@ -340,7 +340,7 @@ A constant value suits a channel whose users all share the value, like the bot a
 <Panel heading="Managing the channel">
 
 Once added, the channel is managed from its details view, described in
-[Dashboard: Channels view](../dashboard/channels-view.mdx#the-channel-s-details-view): the view's header carries the
+[App: Channels view](../dashboard/manage-an-app/channels-view.mdx#the-channel-s-details-view): the view's header carries the
 **Pause**/**Resume** button and the **⋮** menu with **Edit** and **Delete**, common to every channel type, and the tabs below the
 header are specific to the channel type.
 
@@ -360,8 +360,8 @@ To pause or resume the channel, click **Pause**/**Resume** in the header; to del
 ![Pause and the channel's menu in the details view's header](./assets/discord-bot_channel-menu.png)
 
 Both actions are explained in the Channels view article, in
-[Pausing and resuming a channel](../dashboard/channels-view.mdx#pausing-and-resuming-a-channel) and
-[Deleting a channel](../dashboard/channels-view.mdx#deleting-a-channel). Each of them also has a Discord side, explained here:
+[Pausing and resuming a channel](../dashboard/manage-an-app/channels-view.mdx#pausing-and-resuming-a-channel) and
+[Deleting a channel](../dashboard/manage-an-app/channels-view.mdx#deleting-a-channel). Each of them also has a Discord side, explained here:
 
 * A paused bot stops answering, and Quill closes its connection to Discord, so the bot appears offline on Discord.  
   Messages users send while the channel is paused do not reach Quill, and will not be answered when the channel is resumed.

quill/channels/overview.mdx

@@ -61,7 +61,8 @@ A channel's type is selected in the **Add channel** menu, described in [Adding a
 
 <Panel heading="Channels and agents">
 
-A channel is added for one of the app's agents, and carries conversations to this agent alone.  
+A channel is added for one of the app's [agents](../dashboard/manage-an-app/app-agents-view.mdx), and carries
+conversations to this agent alone.  
 The following holds for channels of every type:
 
 * **An agent can serve several channels at once.**  
@@ -78,16 +79,16 @@ The following holds for channels of every type:
 <Panel heading="Adding and managing channels">
 
 Channels of every type are added and managed in the same places of Quill's management dashboard, described in
-[Dashboard: Channels view](../dashboard/channels-view.mdx).
+[App: Channels view](../dashboard/manage-an-app/channels-view.mdx).
 
 * **Adding a channel starts with selecting the channel's type in the Add channel menu.**  
-  The menu opens from the [Channels view](../dashboard/channels-view.mdx#adding-a-channel), from the
-  [channels list in the app's Overview](../dashboard/channels-view.mdx#an-additional-entry-point-the-channels-list-in-the-overview),
+  The menu opens from the [Channels view](../dashboard/manage-an-app/channels-view.mdx#adding-a-channel), from the
+  [channels list in the app's Overview](../dashboard/manage-an-app/channels-view.mdx#an-additional-entry-point-the-channels-list-in-the-overview),
   and at the last stage of the [Add agent wizard](../getting-started/adding-an-ai-agent.mdx#saving-the-agent), right after an
   agent is created.  
   Selecting a type opens the type's form, described in the type's article.
 * **Once added, a channel is managed from its details view.**  
-  The [details view](../dashboard/channels-view.mdx#the-channel-s-details-view) opens from the channel's box in the Channels view.
+  The [details view](../dashboard/manage-an-app/channels-view.mdx#the-channel-s-details-view) opens from the channel's box in the Channels view.
   The view's header carries the **Pause**/**Resume** button and the **⋮** menu with **Edit** and **Delete**, common to every
   channel type, and the tabs below the header are specific to the channel type.  
   The tabs and the other type-specific parts of the view are described in the type's article.
@@ -96,15 +97,16 @@ Channels of every type are added and managed in the same places of Quill's manag
 
 <Panel heading="Binding agent parameters">
 
-Some agents have **parameters**: values the agent's queries require, and that must come from the channel rather than be chosen by
-the LLM, like the phone number of the customer whose orders the agent looks up.  
+Some agents have [parameters](../dashboard/manage-an-app/app-agents-view.mdx#agent-parameters): values the agent's
+queries require, and that must come from the channel rather than be chosen by the LLM, like the phone number of the
+customer whose orders the agent looks up.  
 Agent parameters are bound by the channel, and the source of a parameter's value depends on the channel type:
 
 * A **bot channel** binds each parameter when the channel is added, to a constant value or to a selected detail of each user who sends
   the channel a message; the user details that can be bound differ by platform, and are listed in each bot's article.  
   A parameter left unbound, e.g., a parameter added to the agent after the channel was added, stops the bot from answering until
   the parameter is bound in the **Parameters** tab of the
-  [channel's details view](../dashboard/channels-view.mdx#the-channel-s-details-view).
+  [channel's details view](../dashboard/manage-an-app/channels-view.mdx#the-channel-s-details-view).
 * A **chat widget** binds the parameters into each embed link
   [when the link is generated](../getting-started/adding-a-chat-widget.mdx#setting-the-link-limits), and a link cannot be generated
   until every parameter has a value.
@@ -150,9 +152,9 @@ Agent parameters are bound by the channel, and the source of a parameter's value
   gets the reply "I can only read text messages right now."
 * **Pausing a channel takes it out of service; deleting a channel removes it.**  
   Both actions are described in the Channels view article, in
-  [Pausing and resuming a channel](../dashboard/channels-view.mdx#pausing-and-resuming-a-channel) and
-  [Deleting a channel](../dashboard/channels-view.mdx#deleting-a-channel). The conversations a deleted channel carried remain
-  available in the app's **Conversations** view.  
+  [Pausing and resuming a channel](../dashboard/manage-an-app/channels-view.mdx#pausing-and-resuming-a-channel) and
+  [Deleting a channel](../dashboard/manage-an-app/channels-view.mdx#deleting-a-channel). The conversations a deleted channel carried remain
+  available in the app's [Conversations view](../dashboard/manage-an-app/conversations-view.mdx).  
   What each action means for the channel's users, and for a bot on its platform, depends on the channel type and is described in
   the type's article.
 * **The messages a channel sends on its own have a default text set by Quill.**  

quill/channels/slack-bot.mdx

@@ -335,7 +335,7 @@ Back in Quill, you can now see the new channel in the Overview's **Channels** se
 2. **Status**  
    **Active**: the channel is enabled; **Disabled**: the channel is paused.  
    Pausing and resuming a channel is described in
-   [Dashboard: Channels view](../dashboard/channels-view.mdx#pausing-and-resuming-a-channel).
+   [App: Channels view](../dashboard/manage-an-app/channels-view.mdx#pausing-and-resuming-a-channel).
 3. **Active links**  
    Embed links belong to web widget channels; a Slack bot channel has none, so the column shows a dash.
 
@@ -447,7 +447,7 @@ A constant value suits a channel whose users all share the value, like the bot a
 <Panel heading="Managing the channel">
 
 Once added, the channel is managed from its details view, described in
-[Dashboard: Channels view](../dashboard/channels-view.mdx#the-channel-s-details-view): the view's header carries the
+[App: Channels view](../dashboard/manage-an-app/channels-view.mdx#the-channel-s-details-view): the view's header carries the
 **Pause**/**Resume** button and the **⋮** menu with **Edit** and **Delete**, common to every channel type, and the tabs below the
 header are specific to the channel type.
 
@@ -467,8 +467,8 @@ To pause or resume the channel, click **Pause**/**Resume** in the header; to del
 ![Pause and the channel's menu in the details view's header](./assets/slack-bot_channel-menu.png)
 
 Both actions are explained in the Channels view article, in
-[Pausing and resuming a channel](../dashboard/channels-view.mdx#pausing-and-resuming-a-channel) and
-[Deleting a channel](../dashboard/channels-view.mdx#deleting-a-channel). Each of them also has a Slack side, explained here:
+[Pausing and resuming a channel](../dashboard/manage-an-app/channels-view.mdx#pausing-and-resuming-a-channel) and
+[Deleting a channel](../dashboard/manage-an-app/channels-view.mdx#deleting-a-channel). Each of them also has a Slack side, explained here:
 
 * A paused bot stops answering. Nothing changes on Slack: the bot remains installed, and Slack keeps delivering the users'
   messages, which Quill discards.  

quill/channels/telegram-bot.mdx

@@ -170,7 +170,7 @@ The new channel appears in the **Channels** section:
 2. **Status**  
    **Active**: the channel is enabled; **Disabled**: the channel is paused.  
    Pausing and resuming a channel is described in
-   [Dashboard: Channels view](../dashboard/channels-view.mdx#pausing-and-resuming-a-channel).
+   [App: Channels view](../dashboard/manage-an-app/channels-view.mdx#pausing-and-resuming-a-channel).
 3. **Active links**  
    Embed links belong to web widget channels; a Telegram bot channel has none, so the column shows a dash.
 
@@ -214,7 +214,7 @@ A user can also start afresh at any moment by sending `/clear`. The bot confirms
 
 In the chat above, the question answered before `/clear` can no longer be answered after it, since the list the question referred to
 is no longer part of the conversation.  
-Clearing also deletes the conversation from the app's **Conversations** view in the management dashboard.
+Clearing also deletes the conversation from the app's [Conversations view](../dashboard/manage-an-app/conversations-view.mdx) in the management dashboard.
 
 </ContentFrame>
 
@@ -320,7 +320,7 @@ A new channel, even one added for the same bot, knows nothing of earlier shares
 <Panel heading="Managing the channel">
 
 Once added, the channel is managed from its details view, described in
-[Dashboard: Channels view](../dashboard/channels-view.mdx#the-channel-s-details-view): the view's header carries the
+[App: Channels view](../dashboard/manage-an-app/channels-view.mdx#the-channel-s-details-view): the view's header carries the
 **Pause**/**Resume** button and the **⋮** menu with **Edit** and **Delete**, common to every channel type, and the tabs below the
 header are specific to the channel type.
 
@@ -340,8 +340,8 @@ To pause or resume the channel, click **Pause**/**Resume** in the header; to del
 ![Pause and the channel's menu in the details view's header](./assets/telegram-bot_channel-menu.png)
 
 Both actions are explained in the Channels view article, in
-[Pausing and resuming a channel](../dashboard/channels-view.mdx#pausing-and-resuming-a-channel) and
-[Deleting a channel](../dashboard/channels-view.mdx#deleting-a-channel). Each of them also has a Telegram side, explained here:
+[Pausing and resuming a channel](../dashboard/manage-an-app/channels-view.mdx#pausing-and-resuming-a-channel) and
+[Deleting a channel](../dashboard/manage-an-app/channels-view.mdx#deleting-a-channel). Each of them also has a Telegram side, explained here:
 
 * A paused bot stops answering, and messages users send meanwhile are held by Telegram for up to 24 hours, to be answered if
   the channel is resumed within this time.