---
title: Set priority and tags
description: >-
  Set announcement priority, optional publish notifications, tags, and draft or
  published status to organise the Info Hub feed and signal urgency.
sidebar:
  order: 8
---

**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](/docs/fuxam-web/base/info-hub/create-an-announcement) or [edit](/docs/fuxam-web/base/info-hub/edit-an-announcement) 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.

:::warning
**Urgent** posts always notify on publish. **Medium** and **High** can notify when you enable **Notify audience when published**. Double-check audience before publishing with notifications enabled.
:::

## 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](/docs/fuxam-web/base/info-hub/search-announcements) 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**.

## Key concepts

| Term | Meaning |
|------|---------|
| **Priority** | Visual urgency level from **No Priority** through **Urgent**; affects badges, card styling, and notification behaviour. |
| **Notify audience when published** | Optional toggle (Medium and High only) that sends in-app and push notifications on publish. |
| **Tag** | Institution-wide label for grouping and filtering announcements. |
| **Status** | Lifecycle state: **Draft**, **Published**, or **Archived**. |

## Priority levels

Set **Priority** on the create or edit form:

| Label | Typical use |
|-------|-------------|
| **No Priority** | Default; no special styling |
| **Low** | Minor updates |
| **Medium** | Notable information |
| **High** | Important updates |
| **Urgent** | Critical, time-sensitive messages |

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](/docs/fuxam-web/base/info-hub/pin-an-announcement)).

:::tip
Reserve **Urgent** for genuine emergencies or hard deadlines — overuse dilutes the red styling and automatic notifications. Routine term-start reminders are usually **Medium** or **High** with the notify toggle enabled.
:::

## 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.

:::note
Notifications reach users in the [targeted audience](/docs/fuxam-web/base/info-hub/target-your-audience) only. Publishing with notifications enabled to **Everyone** notifies the whole institution — double-check audience before you publish.
:::

## 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

1. On the create or edit form, open the **Tags** selector.

2. Pick existing tags from the list, or create a new tag if you can create announcements.

3. Remove a tag by deselecting it before saving.

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](/docs/fuxam-web/base/info-hub/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**:

| Status | Meaning |
|--------|---------|
| **Draft** | Visible to editors only; not shown to the general audience |
| **Published** | Live for everyone in the selected audience |
| **Archived** | Hidden from active views but retained in the system |

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).

:::info
Scheduled publish or archive dates are not available in the UI.
:::

Only **Published** posts appear in audience feeds, trigger read receipts, and can be [pinned](/docs/fuxam-web/base/info-hub/pin-an-announcement). **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

| Combination | Reader experience |
|-------------|-------------------|
| **Draft** + any priority | Editors see the post in draft filters; audience does not |
| **Published** + **High** + notify on | Feed badge, possible push notification, read tracking begins |
| **Published** + **Urgent** + pinned | Red card border, red Home banner, always notifies |
| **Published** + tags | Tag chips on cards; clickable filter in feed |
| **Archived** | Hidden from default feed; searchable with Status filter |

## 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](/docs/fuxam-web/base/info-hub/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

| Pitfall | Consequence | Prevention |
|---------|-------------|------------|
| **Urgent** for non-urgent content | Readers ignore red styling and notifications | Reserve **Urgent** for true emergencies |
| Forgetting notify toggle on **Medium** | Important post publishes silently | Use **High** when you need notifications, or confirm toggle state before **Publish** |
| Inconsistent tag spelling | Duplicate tags ("Exam" vs "exams") fragment filters | Agree on a shared tag list |
| Publishing a **Draft** meant for review | Audience sees unfinished content | Use **Draft** button explicitly; filter feed by Status while reviewing |
| Expecting scheduled publish | Post stays Draft until manually published | Plan manual publish time; no scheduler in UI |

## FAQ

**Can I change priority after publishing?**

Yes. [Edit the announcement](/docs/fuxam-web/base/info-hub/edit-an-announcement) and save. Changing to **Urgent** on update does not retroactively change notification behaviour for the original publish — plan priority before the first **Publish** when notifications matter.

**Who can create new tags?**

Users with permission to create announcements can create tags from the tag selector on the form.

**Do Low priority posts notify anyone?**

No. The **Notify audience when published** toggle is hidden for **No Priority**, **Low**, and **Urgent** (urgent has its own always-notify path).

**Can readers filter by priority?**

Yes. All users can filter the Info Hub feed by priority. Editors can additionally filter by status and visibility. See [Search announcements](/docs/fuxam-web/base/info-hub/search-announcements).

## Related pages

**[Create an announcement](/docs/fuxam-web/base/info-hub/create-an-announcement)**

Set priority, tags, and status on a new post.

**[Pin an announcement](/docs/fuxam-web/base/info-hub/pin-an-announcement)**

Combine pinning with priority for Home dashboard emphasis.

**[Search announcements](/docs/fuxam-web/base/info-hub/search-announcements)**

Filter the feed by priority, tags, status, and more.

**[Target your audience](/docs/fuxam-web/base/info-hub/target-your-audience)**

Notifications are sent only to the selected audience.

**[Info Hub overview](/docs/fuxam-web/base/info-hub)**

Full announcement lifecycle and key concepts.
