Skip to content

on the dashboard/servers/{guildid} page, when showing a guild manager t… - #13

Merged
quarterback-ai-dev-environment[bot] merged 1 commit into
mainfrom
qb/int-0006-on-the-dashboard-servers-guildid-page-wh
Aug 20, 2026
Merged

on the dashboard/servers/{guildid} page, when showing a guild manager t…#13
quarterback-ai-dev-environment[bot] merged 1 commit into
mainfrom
qb/int-0006-on-the-dashboard-servers-guildid-page-wh

Conversation

@quarterback-ai-dev-environment

Copy link
Copy Markdown
Contributor

Intent

on the dashboard/servers/{guildid} page, when showing a guild manager their list of channels, there should be a special icon or word next to channels that the bot is restricted from posting in. maybe saying "(restricted)" next to the channel name. After clicking the "save reporting channel" button, instead of saving immediately, there should be a confirmation modal popup that restates the current channel and the new channel, and IF the new channel is restricted, we should put some kind of warning that the manager must grant RowBot access to that channel or the messages will be rejected. Despite the warning, the user can still click" confirm" or "cancel". Ideally this would only reload the relevant part of the page via htmx instead of reloading the whole page. The save button should be an htmx post rather than a standard submit.

Claims proven

  • The confirmation dialog restates both the currently-configured reporting channel and the newly-selected channel, so the manager sees exactly what is changing. (CAN)
  • The confirmation dialog always contains a static warning to the effect of "the bot must be granted permission to post in this channel", shown unconditionally with no per-channel restriction detection. (MUST)
  • No per-channel bot-permission (restriction) detection is added — the channel list and save path still read only channel id/name/type and do not fetch or compute SEND_MESSAGES permission. (MUST)
  • From the confirmation dialog the manager can confirm (which performs the save) or cancel (which makes no change and closes the dialog); the warning is informational and does not disable or block the confirm control. (CAN)
  • The reporting-channel save is submitted as an htmx post to POST /dashboard/servers/{guildID}/channel. (CAN)
  • On a successful reporting-channel save via htmx, only the relevant part of the dashboard page is updated via an htmx partial swap, rather than triggering a full-page reload/navigation. (MUST)
  • On the per-guild dashboard page, clicking "Save reporting channel" opens a confirmation dialog and does NOT save the channel until the manager confirms — the submit no longer posts to /dashboard/servers/{guildID}/channel directly on click. (MUST)

Confidence: high

Closes #12

Authored-by: Quarterback <engine@qback.com>
@quarterback-ai-dev-environment
quarterback-ai-dev-environment Bot merged commit cfb634c into main Aug 20, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment