InfoIQ

The builder

An announcement is a sequence of pages, not a block of text. Each page carries a title, rich content and an optional image or video, and the author sees the reader's view while composing. Pages can be reordered — by dragging, or with the move controls — and previewed before anything is published. A PowerPoint deck imports as one page per slide, so there is nothing to rebuild by hand.

Readers can ask the author a question from inside the announcement. Questions are private between the reader and the author until the author chooses to publish an answer, at which point everyone targeted by the announcement sees it.

Targeting

Rather than static lists, InfoIQ targets by rule. A rule combines criteria — profile, role, public group, queue, application, and the other criteria supported by the package — and the announcement reaches whoever matches at delivery time. People who join a team next month are covered by the rule that was written last month.

A set of criteria your team reuses can be saved as a named audience and applied to any number of announcements. An audience in use by a live announcement is locked, so nobody can quietly change who a running campaign reaches.

An unrecognised criterion never silently widens an audience: it is treated as no restriction only after being logged, so a misconfiguration is visible rather than invisible.

The reading experience

Recipients receive the announcement as a modal in the Salesforce app they already use. They page through it, and can close it and reopen it later — it opens at the first page each time. The package records how far they got: which pages they reached, and how deep into the announcement they went.

Analytics

Two measures, kept deliberately distinct:

• Reach — how many targeted people opened the announcement at all.
• Attention — how far into it they got, page by page.

An announcement deleted from inside the application keeps contributing to your corpus statistics: a snapshot of its figures is written before the deletion, so a year of reporting is not quietly rewritten by a spring clean. A record removed outside the application — by Data Loader or the API — bypasses that snapshot, which is a reason to retire announcements from the app rather than in bulk.

Permissions

The package ships permission sets for the two personas it recognises. Managers build, publish and read the analytics. Recipients read what they were sent — and nothing else: a recipient cannot enumerate who read an announcement, nor read the questions their colleagues asked. That separation is enforced by the platform's sharing model, not by hiding buttons in the interface. A third permission set exists only for a data migration: it carries a custom permission that lets imported announcements keep the dates they originally went out on, and it is meant to be taken back once the import is done.

Setting it up takes one of those permission sets and one component: the Announcement Host, dropped on the pages where people work or added once to an app's utility bar. The whole setup fits in two minutes:

Documentation

The administrator and user guide covers installation, the permission sets, building an announcement page by page, writing targeting rules and reading the analytics. It is published on this site rather than behind a login, so you can read the whole thing before installing anything or talking to anyone.

Requirements

Salesforce editions

Enterprise, Unlimited and Developer editions

Deployment

Managed package installed from AppExchange. No external components to host.

Lightning Experience

Required. The reading experience is a Lightning Web Component.

API version

65.0

Salesforce security review

[TO COMPLETE: Status, e.g. 'Submitted, review in progress' or 'Passed on ']

Documentation

Administrator and user guide, also available as a PDF.