Set priority and tags

Set announcement priority, optional publish notifications, tags, and draft or published status to organise the Info Hub feed and signal urgency.

Priority, tags, and status are the metadata layer on every Info Hub announcement. Together they control how prominently a post appears in the feed, whether readers receive a notification when you publish, how easily people can find related posts later, and whether a draft is still internal or live for your audience. You set all three on the create or edit form — and they interact: an Urgent pinned post looks different on Home than a Low priority routine update, and only certain priority levels expose the Notify audience when published toggle.

Why it matters

Not every institutional message deserves the same visual weight or the same push to mobile devices. A cafeteria menu change and a campus closure are both “announcements”, but treating them identically erodes trust in urgency signals. Priority gives readers an at-a-glance sense of importance; tags create a durable taxonomy for filtering and discovery; status separates work-in-progress drafts from live communications and retired archives.

For administrators, consistent use of priority and tags makes the Info Hub scalable: editors can search and filter by tag or priority, students learn that Urgent means act now, and compliance teams can confirm a Published policy post was not left in Draft.

How it fits

Priority and tags are configured on the same form as audience targeting and optional pinning. The typical workflow is: draft content → set audience → choose priority and tags → save as Draft for review or Publish immediately.

Notifications on publish complement — but do not replace — the Info Hub feed. Medium and High priority posts can trigger in-app and push notifications; Urgent always notifies. Delivery still respects each user’s personal notification preferences on Fuxam Mobile — see Use the notification center.

Key concepts

Priority levels

Set Priority on the create or edit form:

Posts with a priority above No Priority show a priority badge on cards and the detail page. Urgent items also get stronger visual emphasis (including a red left border on cards and a red pinned banner when pinned).

Notify on publish

The Notify audience when published toggle appears when priority is Medium or High.

• When enabled and you Publish, Fuxam sends in-app and push notifications to users in the announcement audience.
• Urgent announcements always notify when published, regardless of this toggle.
• The setting is hidden for No Priority, Low, and Urgent (urgent uses its own always-notify behaviour).

Notification delivery still depends on each user’s personal notification preferences.

Tags

Use Tags to label announcements for filtering and discovery. Tags are shared across the institution: once created, any editor with permission can apply them to new posts.

How to add or remove tags

Tags appear as chips on announcement cards (up to two on compact views) and on the detail page. Clicking a tag on a card can filter the Info Hub feed to that tag.

Tag naming guidance

Consistent tag names pay off when staff use Search announcements or filter by tag from the filter panel. Consider a small institution-wide vocabulary — for example, “registration”, “exams”, “housing”, “IT” — rather than one-off tags per post that fragment discovery.

Status

Every announcement has a status:

Save status using the header buttons (Draft or Publish / Update & Publish) on the form, or change status from the detail page actions menu (Update Status submenu).

Only Published posts appear in audience feeds, trigger read receipts, and can be pinned. Archived posts drop out of default feed views but remain available to editors with appropriate filters — useful when a deadline passes but you want to retain the record.

How priority, tags, and status work together

Best practices

• Match priority to action required. If readers only need to know something eventually, Low or No Priority is enough. If they must act by a date, High or Urgent is appropriate.
• Use tags for themes, not for urgency. Priority already signals importance; tags should help people find “all exam-related posts” months later.
• Keep drafts in Draft until reviewed. A premature Publish with High priority and notifications enabled cannot be unseen — audience members may already have a push notification.
• Archive instead of delete when a notice expires but you want audit history. Use Delete an announcement only when the post should be removed entirely.
• Align tag vocabulary across faculties where possible, so central communications and school-level editors filter consistently.

Common pitfalls

FAQ

Related pages