Project updates

Projects need Org plan.

An update is the narrative record: what happened, in text and images. The corresponding measurement is evidence, and both are generally required.

An update comprises a caption, media, and optionally a link and a location.

Three constraints apply:

Captions support inline formatting but not structure. The toolbar provides bold, italic, underline, links and hashtags; typing #something marks it as a hashtag. Headings, lists and embedded blocks are not available, so a caption is one or more paragraphs rather than a document. Where structure is required, use multiple updates or attach a file.

Captions are limited to 2,200 characters. Content exceeding this generally belongs in an attached document or a wiki page.

A link preview is captured once, at the time of posting. The title, description and image are read from the target page at that moment and stored. Subsequent changes to the page are not reflected: the link continues to work, but the preview is a snapshot rather than a live view.

System-generated updates

Completing a milestone generates an update automatically. These are marked as system-generated and cannot be edited or rewritten. Where a system update states something incorrect, amend the milestone rather than the post.

Who can see an update

Four levels are available:

Visibility	Who sees it
Public	Anyone, including people with no account
Org	Anyone in the organisation that owns the project
Members	Only people explicitly added to the project
Funders	Your funders — see below

The default is Public. The composer opens at this setting, so an update published without changing it is visible to anyone, including users without an account. Set the visibility before publishing.

Funders is an enforced audience rather than a label. A member qualifies where they belong to a funder organisation holding an active funding relationship with the project. This allows reporting to funders without publishing publicly and without adding them to the project.

This tier is intended to replace reporting by email. Material written for a funder should be posted here rather than sent.

Note that org and members are distinct: organisation membership does not confer project membership. See Project or workspace?.

The project feed — updates as the public sees themOpen /p in the app

×

The feed offers two views, Table and Gallery. Each post displays its state and audience, so the visibility of a published update can be confirmed without opening it.

Publishing and drafts

The composer provides Save draft and Publish now as separate controls. A draft remains in the feed marked as such and is published only on the publish action.

The composer also retains unsaved text. Closing it mid-entry preserves the content, which is offered again when the composer is next opened.

Changing and removing updates

An update can be edited or deleted after publication, and updates can be published, unpublished or deleted in bulk from the list.

Unpublishing is generally preferable to deletion. It removes an update from view without destroying it, which is the appropriate response where something was published prematurely or to the wrong audience. Deletion is irreversible.

The exception is the system-generated updates produced by a completed milestone, which cannot be edited or rewritten.

Your projectsProjects