Announcements show site statements, model changes, maintenance notices, and operational messages to signed-in users. Administrators control content, type, status, priority, pinning, and display window.

Entry Point#

Open Announcements in the admin console. The page supports searching by title or content, and filtering by status, type, and pinned state.

After an announcement is updated, users see the new version. Use announcements for changes that affect user experience, such as model adjustments, file processing maintenance, billing rule changes, or temporary service notices.

Announcement List#

The list shows title, type, pinned state, status, priority, and display window. Status can be active or inactive. Types include critical, warning, info, normal, and general.

Priority controls ordering when multiple announcements exist. Pinned announcements are useful for long-running important information or notices that should be read first.

Create Announcements#

Use Create to fill title, type, priority, pinned state, status, display window, and content. Content supports Markdown and includes a preview.

Titles should be short and clear, such as “June model maintenance”, “File retrieval policy update”, or “Billing rule change”. Content should explain impact, start time, duration, user action, and support contact.

Display Window#

Announcements can be always active or limited by start and expiration time. Always-active announcements fit terms, usage notes, and common reminders. Timed announcements fit maintenance windows, temporary incidents, and events.

Set start and expiration times for temporary messages so outdated notices do not keep distracting users.

Enable, Disable, and Delete#

Disabling an announcement hides it while keeping the configuration, useful for temporary removal or later reuse. Deleting removes it from the management list and does not affect other user data.

Delete confirmed one-off notices that are no longer needed. Keep reusable templates disabled instead of deleting them.

Practical Tips#

For critical notices, put impact and required action first, then background. Maintenance notices should include time, affected features, and expected recovery. Do not include secrets, internal addresses, or administrator-only details in announcements.