Discord settings: no way to unlink a server, and org owners have no Discord view (all routes platform-admin only) #221
Open
opened 2026-10-04 20:07:43 -04:00 by logan
·
3 comments
No Branch/Tag Specified
Labels
Clear labels
area/ai-pipeline
area/auth
area/billing
area/correlation
area/discord
area/frontend
area/governance
area/growth
area/infra-deploy
area/legal
area/map
area/mqtt
area/node-ota
area/osint
area/recording-audio
area/sdr-radio
area/transcription
board
board:agenda
minutes:draft
minutes:final
role:ceo
role:cfo
role:cio
role:ciso
role:cmo
role:coo
role:cto
Scene/entity extraction, summarizer, AI providers, embeddings
AuthN/Z, roles, tenancy/org scoping, API keys, credentials
Plans, entitlements, AI spend accounting and caps
Incident correlation, linking, lifecycle, severity, corr_debug
Discord bot, radio bots, voice streams, bot tokens, webhooks
Web UI: Next.js app and the edge-node local dashboard
Board process, minutes, unattended runner, agent tooling
Go-to-market, outreach, cold email, discovery conversations
CI/CD, VM, registry, Firestore rules/indexes deploy, Terraform/Caddy
ToS, retention, licences/DAAs, CAN-SPAM, E&O, name suppression
Live map: pins, paths, tiles, legend, geocoding
Node-C2 MQTT, checkins, commands, node sweeper, dynsec
Node install, enrollment, OTA updater, image skew
External feeds: cameras, 511, ADS-B, AIS, outages, and their licences
Call capture, boundaries, PulseAudio, ring buffer, trimming, attribution
OP25 decode, SDR hardware/tuning, conventional, second SDR, mesh radio
STT, transcript correction, place verification, name accuracy
Board process: minutes and board-filed items
Needs board scoping at the next sitting; CEO removes the label once scoped
One exec pre-read, closed by CEO
CEO ruling; open until enacted
Filed by the CEO
Filed by the CFO
Filed by the CIO
Filed by the CISO
Filed by the CMO
Filed by the COO
Filed by the CTO
kind
behavior-bug
Wrong product behavior; the instrument reads it correctly
kind
measurement-bug
Corrupts the recording/instrument (debug data, evals, health checks), not behavior
priority
p0
Drop everything: prod broken, live exposure, or owner-ruled P0
priority
p1
Next up: blocks a gate, a customer, or core incident quality
priority
p2
Normal: real defect or planned work, schedule in turn
priority
p3
Low: minor, cosmetic, or someday
status
blocked
Waiting on an external party, spend, or another issue
status
in-progress
Branch or PR open against it
status
needs-decision
Waiting on an owner or board ruling before work
status
needs-info
Root cause or repro unknown; needs a reading first
type
bug
Something built is wrong: code, data, or a measurement
type
chore
Maintenance, refactor, tests, pinning, cleanup: no user-visible change
type
decision
A ruling to make or record: board minutes, owner calls, legal reviews
type
docs
Docs, runbooks, CLAUDE.md, skills, SOPs
type
feature
New capability or an extension of an existing one
type
security
Security, privacy, credential or tenant-isolation exposure
type
tracking
Tracker, checklist, initiative or punch-list spanning several changes
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: logan/server-26#221
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found while building the Discord admin page (PR #219, server-26#213 item 2).
PUT /discord/guilds/{id}/linkcan set or move a server's org, but nothing deletes adiscord_guildsdoc. A server removed from an org stays linked to it (or must be re-linked to some other org)./settings/discordis platform-admin only because every route behind it isrequire_admin_token(GET /discord/admin/overview,/tokens, link). The design (design-canvas/discord-system-notes.md, "Settings > Integrations > Discord") is an org-owner page: their own servers, their own radio channels, invite links for bots that can serve them. Needs org-scoped read routes (overview filtered byacting_org_id, bots filtered to pool + their BYO, no token internals) and owner-level stop/start. Same shape as the DEFERRED.md entry for/settings/members(owner reaches the page, every request 403s) - this one avoids that by hiding the tab, so today an owner simply has no Discord surface.Pairs with #213 item 1 (self-serve
/drb link), which is the natural place to add the owner view.PR #218 (feat/213-guild-link, #213 item 1) covers item 1 here for org owners:
DELETE /discord/linked-guilds/{id}unlinks the caller's own server (setsorg_idnull +unlinked_at, stops its streams, never falls back toDISCORD_UNLINKED_GUILD_ORG_ID), andGET /discord/linked-guildsgives owners a list of their linked servers on Settings -> Organization. Item 2's org-scoped channels/bots view is NOT in #218 - still open here. Close item 1 when #218 merges.PR #224 adds the missing removal half: #224
DELETE /discord/guilds/{id}(admin) deletes a server's radio channels and unlinks it with #218 semantics plusremoved_at, so it never falls back toDISCORD_UNLINKED_GUILD_ORG_ID.DELETE /discord/streams/{id}(admin) andDELETE /discord/nodes/{node}/streams/{id}(org owner or admin) remove single radio channels.Item 2 here (an org-owner Discord view: channels and bots filtered to their org) is still not built. Org owners get Remove only on the node page.
New detail from #225 S3 (PR #249):
PUT /tokens/{id}/prefer/{system_id}now lets an org owner mark their own BYO bot as preferred for their own org's system (owner decision Q2). But an owner still has no way to learn their BYO bots'token_ids, becauseGET /tokensis admin-only and the new voice-check returns bot names only. The org-scoped bot list in item 2 here (pool + own BYO, no token internals) should includetoken_idandpreferred_for_system_idfor the org's own BYO bots, so the owner UI can call/prefer.