Create an announcement

Create a new Info Hub post with title, rich-text body, attachments, audience targeting, and draft or published status.

Create an announcement is how you add a new post to the Info Hub. The creation flow collects everything readers need — title, body, attachments, audience, priority, and tags — and lets you save as a Draft for internal review or Publish immediately to your chosen audience.

Why it matters

Most institutional communication failures are not about writing quality; they are about reach and timing. A registration reminder sent only by email may never reach students who live in the app. A notice posted to everyone when only one cohort is affected creates noise and trains people to ignore the feed. Creating an announcement through the Info Hub gives you a structured, auditable publish path with deliberate audience control, optional urgency signalling, and automatic read tracking once the post is live.

How it fits

Creation is the first step in the announcement lifecycle. Before you start, consider:

• Who needs to see this? — Target your audience using Everyone, institution roles, individual users, user groups, or study-program cohorts.
• How urgent is it? — Priority and tags affect visual prominence and whether readers receive a push notification on publish.
• Will you repeat this format? — Templates pre-fill structure and placeholders for recurring notices (welcome letters, exam instructions, term-start checklists).

After publishing, readers encounter the post in the Info Hub feed, the Home widget, and optionally the pinned banner. On Fuxam Mobile, Medium- and High-priority publishes may surface in the notification center. This is separate from Chat, which remains the right channel for conversational back-and-forth.

Start a new announcement

Alternatively, open Templates, click Assign on a template, or start from a template-linked create flow to pre-fill content from that template.

Fill in the form

The creation form is organised in sections:

Title and template (optional)

• Title — required; up to 200 characters.
• Select Template (Optional) — pick a saved template to pre-fill the body and placeholders. You can change everything before publishing.

Choose a title that reads clearly in feed cards, the Home widget, and mobile notifications — readers often see only the title before deciding to open the post.

Target audience

Choose who can see the post. See Target your audience for full detail on Everyone vs Targeted Audience.

Content

• Content — rich-text body (headings, lists, formatting, links).
• If you selected a template with placeholders (such as a recipient name or event date), fill in those values in the placeholder section before publishing.

Use headings and short paragraphs so the post scans well in the detail view and in the pinned banner when expanded.

Attachments

• Attachments — optional files (images and documents) that readers can open from the published post.

Attach PDFs or images when the announcement references forms, maps, or visual instructions readers will need after opening the post.

When semantic search is enabled for your institution, Fuxam also reads the text inside supported document attachments and includes it in the announcement’s search index and in the Similar Content check. Text is extracted from these attachment types:

Priority, tags, visibility, and pin

In the settings section you can set:

• Priority — from No Priority through Urgent (see Set priority and tags).
• Notify audience when published — for Medium and High priority only.
• Tags — assign existing tags or create new ones.
• Who can see this? — Everyone or Targeted Audience.
• Pin to dashboard — optionally pin when saving (requires permission to pin announcements to take effect for readers).

Reserve Urgent and notification-enabled publishes for genuinely time-sensitive items so mobile and feed attention stays meaningful.

Similar content detector

When your institution has semantic search enabled, a Similar Content section scans your draft while you type and warns if similar posts already exist. The check compares your title and body — and the extracted text of supported document attachments — against existing announcements.

This helps avoid duplicate notices (for example, two posts about the same exam date). If a similar post already covers the topic, consider editing the existing announcement instead of creating a new one.

Save or publish

Use the actions in the page header:

Publish requires both a title and body. After a successful save, you are redirected to the announcement detail page.

Best practices

• Draft first for sensitive content — policy changes and leadership communications benefit from a Draft review before Publish.
• Match audience to scope — use cohorts for intake-specific notices and user groups for cross-cutting staff teams.
• Tag consistently — tags power filters on the main feed; agree on a small vocabulary (for example, “Exams”, “Campus”, “IT”) with your communications team.
• Attach searchable documents — when a PDF or Office file carries key detail, attaching it also makes that text findable in search and duplicate detection, not just readable after opening.
• Use templates for repetition — standardise welcome and deadline formats so authors spend time on substance, not layout.

Common pitfalls

FAQ

Related pages