Updates

What readers see

Open Updates to read the published feed. For you highlights up to two of the newest updates selected for your learning groups or teams. The remaining items appear under More updates; when there are no matching recommendations, the feed shows All updates.

Updates are ordered by their feed date. A correction can change the article without moving it forward in the feed. Authors can deliberately renew that position when the update needs attention again.

An audience makes an update relevant; it does not restrict access. Everyone admitted to the installation can read all published updates. Updates have no completion requirement or due date, and a reader’s feedback rating is not an acknowledgement that they read it.

On a public installation, an Administrator may also choose recommendations for guests. Those recommendations do not give a guest team membership or an account assignment.

Create an update

Contributors and Administrators can create and publish Updates.

1. In Account menu, open Manage content or Manage organization, then Content. Select Update.
2. Add the title and body. Explain the change, its effect, and any action readers need to take.
3. In Details, add a Short description and choose or create a Category.
4. Choose the audience and Card artwork.
5. Resolve the items under Before publishing, then select Publish.
6. Open Updates and check the card and article.

Keep maintained instructions in a doc when readers will need a current reference after the announcement. An update can explain why an expense policy changed and link to the doc containing the current policy.

Select the audience

In the update’s Details, open Audience to select who receives it in For you.

• Contributors can change the selected learning groups.
• Administrators can change learning groups and teams.
• Existing team selections remain in place when a Contributor edits the update; Contributor access does not permit changing them.

Learning-group relevance includes people who belong through linked teams. A selected team covers its branch, including teams beneath it. Selecting overlapping audiences does not create multiple copies of the update for a reader.

Save the audience choices to the draft and publish the update to make them live. Removing an audience takes away that source of relevance; another selected group or team may still make the update relevant to the same person.

Learning groups and Reporting teams explain how audience membership is maintained.

Correct an update or bring it forward

Open the existing update in Content and revise it. Changes save as a draft until you publish.

For a minor correction, leave Bring this update to the top unchecked under Details → Publishing. Publishing replaces the article while preserving its feed position.

For a change that deserves renewed attention, select Bring this update to the top before publishing. The publication moves the update forward in Updates and in For you for its selected audience. It remains the same update with the same link; it does not become a duplicate announcement.

If the material should leave the published library, use Unpublish from its Content actions. The editor covers unpublishing, reverting a draft to the published copy, and recovering unsaved changes.