Urgent Approved: NexGenSphere + Sam (HK) Needs Discord admin to execute

Magno Discord — replicate HK "prop firm" channel

Execution handoff · Subject brand: MagnoFX · Requested by Nick Jones (Fewpips Marketing)

"You know how we have a channel on HK discord called prop firm — can we please do the same for magno? @NexGenSphere and Sam from HK are both aware and have approved this."

Why this is a handoff, not an auto-action

The AIM runner has no Discord credentials (only Telegram bot tokens) and cannot read the HK server's channel settings nor create a channel on the Magno server. Creating the channel is a live Discord-admin action — it must be run by whoever holds Magno Discord admin (Veljko / Djordje). Everything needed to do it in ~2 minutes is specified below.

What to create on the Magno Discord

FieldValue
Channel nameprop firm → Discord stores it as prop-firm (spaces auto-hyphenate). Match HK exactly.
TypeText channel (same type as HK's — confirm it isn't an Announcement/News channel; if HK's is Announcement, create it as Announcement so it can be followed/crossposted).
CategoryPlace under the same category HK uses (e.g. an "Info" / "Official" / top category). Mirror HK's ordering.
TopicCopy HK channel's topic string verbatim.
PermissionsMirror HK: typically @everyone = View ✔ / Send Messages ✖ (read-only/broadcast), staff role = Send ✔. Copy the exact overwrites from HK.
SlowmodeMatch HK's slowmode value (often off for read-only channels).
Pinned / intro postReplicate HK's pinned message(s) / first post, adapted so brand references read Magno not HK.

Fastest way to mirror exactly (do this side-by-side)

  1. Open the HK Discord → right-click the prop firm channel → Edit Channel. Note: type, category, topic, slowmode, and every entry under Permissions.
  2. On the Magno Discord → right-click the target category → Create Channel → same type → name prop firm.
  3. Edit the new channel and reproduce topic + slowmode + permission overwrites from step 1.
  4. Re-create HK's pinned/intro content, swapping HK brand wording for Magno.
  5. Post the go-live confirmation (see below) so Nick can be updated in the thread.

Context worth carrying over

This follows the recent impersonator cleanup on Magno (predatory DM accounts were kicked). If the HK "prop firm" channel carries an official-warning / "we do not DM you" notice, replicate that here too — it reinforces the anti-impersonator message Nick asked about earlier in the same thread.

CONFIRM before go-live

Who executes: Veljko / Djordje (Magno Discord admin). Approvals from @NexGenSphere and Sam (HK) are already on record in the thread, so no further sign-off is needed — just the mirror + go-live. AIM runner does not post to Discord/Telegram or the client per policy.

Runner note: AIM Master runner cannot perform Discord actions (no Discord token/guild access). This page is the execution spec only. CRM task opsbot_n5210661013_928_1859460283.