# Announcements Source: https://docs.settlemint.com/docs/console/asset-lifecycle/venues/announcements Publish, schedule, edit, attach to and withdraw venue announcements for the whole venue or one instrument. An announcement is a notice to the participants of the whole venue or of one instrument. A wallet that holds the "Venue operator" or "Venue admin" role on the venue writes one on the venue's **Announcements** tab, and those roles are granted on the venue's [Permissions](https://docs.settlemint.com/docs/console/asset-lifecycle/venues/permissions) tab. The platform adds the notice to each participant's notification list, which the Platform API serves, and emails the participants who have email switched on for it. [Participant alerts](https://docs.settlemint.com/docs/console/asset-lifecycle/venues/participant-alerts) sets the default for that email. ![The venue's Announcements tab with the Publish announcement button and the announcements table with Title, Audience, Severity, Status, Published and Actions columns](https://docs.settlemint.com/docs/screenshots/console-venue-announcements.light.en.webp) [Screenshot] The DALP Demo Exchange "Announcements" tab, with search, the "Severity" and "Status" filters and the "Publish announcement" button. The table lists two notices with severity "Warning" and status "On display", each with a "Withdraw" action. An opened row shows the notice's **Announcement history**. ## Before you start [#before-you-start] - **A wallet that operates the venue.** Publishing, editing or withdrawing a notice needs the "Venue operator" or "Venue admin" role and a wallet verification. - **A PDF, if the notice needs a document.** Each file is limited to 10 MiB, or to the lower limit your deployment sets. ## Steps [#steps] ### Write and publish the notice [#write-and-publish-the-notice] 1. Select **Publish announcement**. Enter the "Title" and the "Message", and pick the "Audience": "Entire venue" or one instrument by its name. A notice on a private instrument reaches only that instrument's participants and operators. 2. To send the notice to specific participants, choose them under **Addressed to**. Only those participants see the notice and are notified, and the history shows the operator who it went to. Leave the field empty to reach everyone in the audience. On a private instrument, each participant you name must hold a wallet on that instrument. 3. Pick the **Category** and the "Severity". The categories are "Notice", "Broadcast", "Trading window" and "Corporate action". The severities are "Information", "Warning" and "Critical". A "Corporate action" notice follows each participant's email setting for corporate actions, and every other category follows the setting for announcements. 4. Leave **Display from** empty to publish now, or enter a later UTC date and time to schedule the notice. "Display until" sets when participants stop seeing it, and it must be later than the time the notice goes live. "Announcement date" is the date the notice carries, and it defaults to the day the notice goes live. "Announcement date" refuses a typed day that does not exist, such as `2026-02-30`, and shows a message under the field. The sheet's "Publish announcement" stays unavailable until you correct or clear that date. 5. Attach one PDF under "Attachment" if the notice needs a document, then select **Publish announcement** and verify your wallet. The notice appears in the table as "On display", or "Scheduled" when you set a later "Display from". ## Read the announcement history [#read-the-announcement-history] The table on the "Announcements" tab lists every notice with its status: "Scheduled", "On display", "Display ended", "Withdrawn" or "Pending approval". A scheduled notice reaches participants, and sends its published webhook, only when it goes live. A notice whose display has ended stays in the table for operators. Open a row to read its **Announcement history**: the date it was announced, when it went or goes live, when it was updated or withdrawn, and when its display ends. Participants see a notice in the announcement banner of the trading desk and in their notification list. The banner marks each notice's severity with its own icon, and a screen reader reads the severity before the title, such as "Warning: …". Only a **Critical** notice is announced as an alert and interrupts a screen reader. An "Information" or "Warning" notice does not interrupt, and a notice that arrives behind the lead one is heard as the new count of folded notices. With more than one notice on display, the banner shows the most severe one and folds the rest behind "Show 2 more announcements", which a screen reader hears as "2 more announcements". For scheduling, attachments, issuer announcements and publication windows, read [the trading venue concept](https://docs.settlemint.com/docs/concepts/issuing-and-markets/trading-venue#announcements). ## Approve or reject an issuer's notice [#approve-or-reject-an-issuers-notice] A holder of the token's Governance or Supply management role can submit a notice about that token through the API, and it waits as "Pending approval". Its row offers **Approve** and "Reject", each after a wallet check. "Reject" first asks you to confirm, and "Keep" backs out. "Approve" puts the notice on display now, or at its go-live time when it is scheduled. One venue operator or venue admin approves it without a second person, and it then reaches holders on every instrument that trades the security, whichever venue lists it. "Reject" withdraws a notice that never went live: participants never see it, no webhook is sent, and its history reads "Rejected". If another operator already decided the notice, the list refreshes and shows the refusal. ## Edit, attach to or withdraw a notice [#edit-attach-to-or-withdraw-a-notice] **Edit** changes the title, message or severity of a notice that is on display or whose display has ended. Enter a "Reason for the change", select "Save changes" and verify your wallet. Participants see the new text marked as updated. The reason stays with the previous version in the notice's revision history and is not shown to participants. **Attach PDF** adds a document to a notice that is scheduled, on display or whose display has ended, up to five PDFs per notice. With five attached, the action says "A notice holds up to 5 PDFs." Each file has the same size limit as at publication. **Withdraw** removes the notice from the participants' view and cannot be undone. A scheduled notice withdrawn before it goes live sends no webhook. ## You should see [#you-should-see] - Find the notice in the table on the **Announcements** tab and check its status: "Scheduled" until its "Display from" time, then "On display". ## Troubleshooting [#troubleshooting] **A notice has no Edit or Withdraw action** A notice with the status **Pending approval** offers "Approve" and "Reject" instead of "Edit" and "Withdraw". A notice that is withdrawn cannot be changed or restored. Edit changes a notice that is on display or whose display has ended. **Publishing is refused** **Display until** must be later than the time the notice goes live. A PDF must fit the size limit, 10 MiB or the lower limit your deployment sets, and a notice holds up to five PDFs. Publishing needs the "Venue operator" or "Venue admin" role on a wallet of yours and a wallet verification. A refused "Announcement date", or an empty "Title" or "Message", keeps "Publish announcement" unavailable. The message under the date field says what to correct. A "Display from" or "Display until" with only part of its date and time filled in also keeps it unavailable: complete the field or clear it. ## API routes [#api-routes] Your systems receive the `trading-venue.announcement.published`, `trading-venue.announcement.updated` and `trading-venue.announcement.withdrawn` webhooks, which the [webhook event reference](https://docs.settlemint.com/docs/api-reference/webhooks/market-events#trading-venue) describes. The tab calls the trading venue routes in the [v2 API reference](https://docs.settlemint.com/docs/api-reference/v2).