Managed embeds

Create a dashboard-managed Discord message that can be updated later.

Before you start

Sign in and select a server you can manage. April needs access to the destination channel and permission to send messages, embed links or attach files as appropriate. Role hierarchy is relevant to associated role changes, not composing a message; see hierarchy.

Draft and publish

1. Open Administration > Embed and create a message. Give it a name and choose a channel.
2. Write content, add an embed or select an image; content alone is valid. For example, create a short rules message. Use the message composer to preview it.
3. Save the draft, then publish when ready. Saving a draft and previewing it do not themselves establish a Discord message. Check the destination channel after publishing.

A draft’s channel can be changed; a published message is edited in its existing channel. On an existing published record, Save as draft saves the edits as Pending and leaves the existing Discord message unchanged. Choose Save & publish to explicitly attempt to update that message. Pending does not guarantee an automatic queued update or retry. If that message is missing, the record returns to draft with no message ID; select a channel as needed and publish again. A Discord message-delete event also resets the tracked record to draft.

The editor can select two image IDs, but the Worker uses only the first. Generic managed messages do not have the user/server formatting context used by welcome or custom commands: do not rely on {user} or {guild} resolving here. There is a total limit of 100 records; non-premium servers have a limit of 20 and a 30-second publish cooldown. A rate-limited publish can remain pending, so a retry is not guaranteed to succeed immediately.

Local draft: review the channel and message preview before publishing.

Message states and options

State or setting	Meaning
Draft	Saved configuration without an established published message; its channel can be changed.
Pending	Saved changes to an existing published record; the old Discord content may remain. Use Save & publish to attempt an update; automatic processing or retry is not guaranteed.
Published	A tracked Discord message exists in its chosen channel. Publishing subsequent edits attempts to update that message.
Content, embed and image	Supply content, an embed or an image. The form allows two image selections, but only the first is used for this operation.

Change or remove

Edit and save the record, or delete it when no longer needed. Deletion attempts to remove the Discord message, then removes the dashboard record even if the Discord deletion fails; check Discord for any remaining message. If the list is empty, create a draft; wait for loading or retry a failed save after checking access. For publish errors, check channel access, message content, limits and permissions before retrying; inspect the record’s status and destination. A reaction-role helper can publish externally: review its message before saving. See reaction roles.

Before setup, see sign in and select a server. For maintainers, see the administration technical record.