---
title: Target your audience
description: >-
  Control who can see an Info Hub announcement using Everyone or targeted roles,
  users, groups, and cohorts — with inclusive OR logic and legacy visibility
  support.
sidebar:
  order: 7
---

**Audience targeting** is how you control who can see an Info Hub announcement. Every post has a **visibility** setting that determines which users in your institution can find it in the feed, on Home, and in search results. You set visibility when [creating](/docs/fuxam-web/base/info-hub/create-an-announcement) or [editing](/docs/fuxam-web/base/info-hub/edit-an-announcement) a post — and getting it right is one of the most consequential decisions in institutional communication, because a mis-targeted notice either reaches the wrong people or fails to reach the people who need it.

:::warning
Audience logic is **inclusive (OR)**: matching **any** selected role, user, group, or cohort is enough. Selecting both **Roles: Student** and **Cohorts: Winter 2026** means students **or** Winter 2026 members — not only students in that cohort.
:::

## Why it matters

Universities communicate to many overlapping populations: all staff, teaching faculty only, a single intake cohort, or a cross-functional project team. Broadcasting everything to **Everyone** trains readers to ignore the feed; over-narrow targeting leaves critical users in the dark. Audience targeting lets you publish one authoritative post to exactly the population that needs it — without duplicating the message across email lists, course announcements, and chat channels.

Because visibility is enforced at the platform level, users outside the audience never see the post in their feed, unread counts, or analytics as part of the target population. That is different from email BCC lists or informal forwards: the Info Hub is the single source of truth for who was meant to see the message.

Audience targeting sits at the centre of the announcement lifecycle. You choose visibility on the create or edit form before you publish; [read receipts and analytics](/docs/fuxam-web/base/info-hub/read-receipts-and-analytics) then compare opens against that same audience definition. [Pinning](/docs/fuxam-web/base/info-hub/pin-an-announcement) does not change who can see a post — it only changes how prominently pinned posts appear for users already in the audience.

Targeting draws on identity and structure defined elsewhere in Fuxam:

| Source | Where it is managed | Typical use in Info Hub |
|--------|---------------------|-------------------------|
| **Roles** | [Roles and permissions](/docs/fuxam-web/base/user-management/roles-and-permissions) in institution Settings | "All students", "Teaching staff", "Course coordinators" |
| **Users** | [User Management](/docs/fuxam-web/base/user-management) | A named individual or a short list of responsible contacts |
| **Groups** | [User groups](/docs/fuxam-web/base/user-management/user-groups) in Campus Management | Manually curated teams — project groups, committees, cross-cohort staff |
| **Cohorts** | [Study programs and cohorts](/docs/fuxam-web/cms/programs-and-planning/study-programs-cohorts) in the CMS | Intake-based student populations — "BBA Winter 2026" |

:::note
Groups and cohorts sound similar but serve different purposes. **User groups** are manually maintained bundles of people — ideal for staff teams or ad-hoc lists. **Cohorts** are academic intake groups tied to a study program version — ideal for student-facing notices scoped to one enrollment wave. See [User groups](/docs/fuxam-web/base/user-management/user-groups) and [Study programs and cohorts](/docs/fuxam-web/cms/programs-and-planning/study-programs-cohorts) for how to create and maintain each.
:::

## Key concepts

| Term | Meaning |
|------|---------|
| **Visibility** | The rule set that determines which users can see an announcement. |
| **Everyone** | All users in the institution can see the post. |
| **Targeted Audience** | Only users matching at least one selected criterion (roles, users, groups, or cohorts) can see the post. |
| **Inclusive OR logic** | A user who matches *any* selected row — roles **or** users **or** groups **or** cohorts — is in the audience. Rows are not combined with AND. |
| **Legacy visibility** | Older posts may still use earlier audience rules (roles-only or named-users-only) from before the current editor model. |

## Visibility modes

When creating or editing, the **Who can see this?** field offers two options:

| UI label | Who sees the post |
|----------|-------------------|
| **Everyone** | All users in the institution |
| **Targeted Audience** | Users who match **any** of the criteria you select below |

When you choose **Targeted Audience**, a **Target audience** section appears. You must select at least one of **Roles**, **Users**, **Groups**, or **Cohorts**, or switch back to **Everyone**. Fuxam validates this before save — you cannot publish a targeted post with an empty audience.

### Target audience criteria

For **Targeted Audience**, add one or more rows:

| Row | What it means | Managed in |
|-----|---------------|------------|
| **Roles** | Users who hold any of the selected institution roles | Institution Settings → Roles and permissions |
| **Users** | Specific named users | User Management |
| **Groups** | Members of selected user groups | Campus Management → Groups |
| **Cohorts** | Members of selected study-program cohorts | Campus Management → Programs |

Audience logic is **inclusive (OR)**: a user who matches roles **or** users **or** groups **or** cohorts can see the announcement.

:::tip
To reach "all students in cohort A **plus** two administrators who are not in that cohort", add a **Cohorts** row for cohort A and a **Users** row for the two named staff. Anyone matching either row is included.
:::

## How to set a targeted audience

1. Open the [create](/docs/fuxam-web/base/info-hub/create-an-announcement) or [edit](/docs/fuxam-web/base/info-hub/edit-an-announcement) form for the announcement.

2. Set **Who can see this?** to **Targeted Audience**.

3. For each audience type you need, click **Select Roles**, **Select Users**, **Select Groups**, or **Select Cohorts**.

4. Pick items in the selector dialog and confirm.

5. Review the selected counts shown on each row, then save or publish the announcement.

After publishing, only users in the resolved audience see the post in their feed, Home widget, and unread badge counts. Editors can confirm the audience summary on the [detail page](/docs/fuxam-web/base/info-hub/view-an-announcement) sidebar.

## Where audience appears for readers

On the detail page sidebar, editors see **Audience** metadata summarising who the post reaches. Cards in the feed show **Everyone** or a breakdown of targeted roles, users, groups, and cohorts when counts are available.

Editors who can create announcements can also filter the main feed by **Visibility** (**Everyone** vs **Targeted Audience**) — see [Search announcements](/docs/fuxam-web/base/info-hub/search-announcements).

## Legacy visibility types

Older announcements may still use earlier audience rules that limited visibility to specific roles only or named users only. The current editor uses **Everyone** and **Targeted Audience** only. Legacy posts continue to respect their original audience rules and may display differently in filters and badges.

If you open a legacy post for editing, the form reflects the current model. When in doubt about who can still see an old post, check the **Audience** metadata on the detail page and review [read receipts and analytics](/docs/fuxam-web/base/info-hub/read-receipts-and-analytics) for the resolved audience size.

## Best practices

- **Default to the narrowest audience that still covers everyone who needs the message.** Institution-wide policy changes belong on **Everyone**; a registration deadline for one intake belongs on that **Cohort**.
- **Use cohorts for student intake communications** — membership is maintained through enrollment workflows in the CMS, so you do not have to rebuild the list each term.
- **Use user groups for staff or cross-functional teams** that are not naturally expressed as a role or cohort — for example, "Exam board 2026" or "Erasmus coordinators".
- **Use roles when the message applies to a job function** across the institution — for example, all users with the "Lecturer" role.
- **Name posts clearly when using targeted audiences**, so readers who see a card in a mixed feed understand why it applies to them.
- **Review counts before publish.** The per-row selected counts on the form are your last sanity check before a targeted post goes live.

## Common pitfalls

| Pitfall | What happens | How to avoid it |
|---------|--------------|-----------------|
| Publishing to **Everyone** by mistake | The whole institution sees a cohort-specific notice | Re-read **Who can see this?** and row counts before **Publish** |
| Expecting AND logic across rows | More users see the post than intended | Remember OR logic; use a cohort or a curated group for tighter scope |
| Targeting a cohort before enrollment is complete | Some intended students may not yet be cohort members | Confirm cohort membership in [Add users to cohort](/docs/fuxam-web/cms/programs-and-planning/study-programs-cohorts/add-users-to-cohort) before publishing |
| Empty targeted audience | Save is blocked by validation | Add at least one row or switch to **Everyone** |
| Assuming pinning widens reach | Pinned banner only appears for users already in the audience | Fix visibility first; then [pin](/docs/fuxam-web/base/info-hub/pin-an-announcement) if needed |

## FAQ

**Can a user see a post if they match more than one criterion?**

Yes. OR logic means matching any single row is enough. Duplicate matches do not change visibility — the user simply sees the post once.

**Do draft posts respect audience rules?**

**Draft** posts are visible to editors with create permission regardless of audience. Only **Published** posts are shown to the general audience according to visibility rules.

**If I add someone to a group after publishing, do they see the post?**

Audience is evaluated against current group and cohort membership when the user accesses the Info Hub. For time-sensitive notices, confirm membership in the targeted [user group](/docs/fuxam-web/base/user-management/user-groups) or [cohort](/docs/fuxam-web/cms/programs-and-planning/study-programs-cohorts) before you publish rather than relying on post-publish changes.

**Can templates have their own audience?**

Yes. Templates support the same **Everyone** / **Targeted Audience** options. When you create an announcement from a template, you can still change audience on the create form. See [Manage templates](/docs/fuxam-web/base/info-hub/manage-templates).

## Related pages

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

Start a new post and set visibility on the create form.

**[Edit an announcement](/docs/fuxam-web/base/info-hub/edit-an-announcement)**

Change audience on an existing draft or published post.

**[User groups](/docs/fuxam-web/base/user-management/user-groups)**

Create and maintain groups used in targeted announcements.

**[Study programs and cohorts](/docs/fuxam-web/cms/programs-and-planning/study-programs-cohorts)**

Manage cohort membership for student-facing targeting.

**[Read receipts and analytics](/docs/fuxam-web/base/info-hub/read-receipts-and-analytics)**

Compare opens against total audience size after publish.

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

How announcements fit into Fuxam Base communication.
