Edit an announcement
Open an existing Info Hub post, change its fields, and save or publish your updates.
Edit an announcement lets you revise a post after it has been created — correcting typos, updating deadlines, narrowing or widening audience, changing priority, or moving between Draft, Published, and Archived status.
Why it matters
Institutional information changes. Exam dates shift, links break, policies are amended, and targeted audiences need refinement after the first publish. Editing keeps a single authoritative post current instead of publishing duplicates that fragment read tracking and confuse readers searching the feed.
Because the Info Hub tracks read receipts, updating an existing published post preserves the announcement’s identity and analytics history. For substantial rewrites, consider whether readers who already marked the post as read need a follow-up notice — the platform does not automatically re-notify everyone on every edit.
How it fits
Editing uses the same form layout as creating an announcement. Changes to Who can see this? immediately affect who can open the post on next load — including audience rows tied to user groups and cohorts. See Target your audience for visibility rules.
Status changes have distinct effects:
- Draft — hides the post from general readers until published again.
- Published — visible to the configured audience in the feed, Home widget, and (if pinned) the Home banner.
- Archived — removed from active views but retained until deleted.
Open the editor
Open Info Hub and find the announcement you want to change.
Either click the announcement card to open it, then choose Edit from the actions menu, or use Edit from the card’s overflow menu on the main list.
The announcement editor opens.
You can also reach the editor from the announcement detail page after viewing the post.
What you can change
The edit form matches the create form. All of the following are editable:
- Title
- Content (rich text)
- Attachments — add new files; existing attachments remain unless removed
- Status — save as Draft, Published, or move to Archived via header actions or the detail page actions menu
- Who can see this? — Everyone or Targeted Audience (roles, users, groups, cohorts)
- Priority and Notify audience when published
- Tags
- Pin to dashboard
If the announcement was created from a template, placeholder fields may still appear when placeholders exist in the content.
When semantic search is enabled for your institution, the Similar Content detector runs while you edit, excluding the current announcement from duplicate matches.
Field reference
| Field | Notes when editing |
|---|---|
| Title | Up to 200 characters; appears in feed cards and notifications. |
| Content | Full rich-text body; template placeholders may still require values. |
| Attachments | Add or remove files; indexed types contribute to semantic search when enabled. |
| Status | Draft hides from readers; Archive retires without deleting. |
| Audience | Tightening audience removes access for users no longer matched; widening exposes the post to new readers. |
| Priority / Notify | Notification on publish applies to Medium and High only — changing priority on an already-published post does not re-send notifications by itself. |
| Pin to dashboard | Requires permission to pin announcements to affect the Home banner for readers. |
Save your changes
Header actions work the same as on create, with labels adjusted for edit mode:
| Button | Result |
|---|---|
| Draft | Saves with status Draft. |
| Update & Publish | Saves and keeps or sets status Published. |
Saving redirects you to the announcement detail page.
Discard changes
There is no separate Discard button. To abandon unsaved edits, navigate away using the breadcrumb, sidebar, or browser back. Unsaved changes are lost unless you save first.
Best practices
- Archive instead of delete when a post is outdated but may be needed for audit — archiving hides it from active views without permanent removal.
- Document major changes in the body — add a short “Updated on …” note at the top so returning readers see what changed.
- Review audience after cohort or group changes — if membership in a targeted user group or cohort shifted externally, the announcement’s audience updates automatically, but the selection in the editor may need manual adjustment for new groups.
- Check Similar Content when rewriting substantially — avoid unintentionally duplicating another live post.
Common pitfalls
| Pitfall | Consequence |
|---|---|
| Reverting to Draft on a live post | Readers lose access immediately until you publish again. |
| Navigating away without saving | All unsaved edits are lost — there is no Discard confirmation. |
| Expecting edit notifications | Notify audience when published applies at publish time; routine edits do not automatically push to mobile notifications. |
| Removing attachments readers rely on | Deleted files disappear from the detail page; consider linking to replacement documents in the body. |
FAQ
Can I change the audience of a published announcement?
Yes. Update Who can see this? and targeted rows, then save. Users newly included gain access; users no longer matched lose access on their next visit.
Does editing reset read receipts?
Opening the post still counts as read for each user. Editing does not clear existing read history — see Read receipts and analytics.
How do I retire an old announcement without deleting it?
Move status to Archived via header actions or the detail page actions menu. Archived posts remain in the system but are hidden from active views.