Catch-Up: getting started
Catch-Up brings Confluence documents and repository updates into a shared news feed, with discussion beneath each post and a private reading place for each person.
Open your feed
After your Confluence administrator installs Catch-Up, open Apps → Catch-Up. Choose an available feed and select Follow to keep it in your navigation. Following a feed does not grant access or subscribe its source documents.
To put a feed in an ordinary Confluence page, edit the page, insert
/Catch-Up, choose the feed and publish the page.
Readers still need access to the feed and its source documents. The published
feed expands with its content and follows Confluence's light or dark theme.
Older posts are above newer posts. Returning readers start at their saved reading place, with a New divider before newer entries. Expand a post's discussion to comment. Seen and saved state belong to you; opening a feed does not mark everything seen, and seen does not mean acknowledged.
Set up one shared feed
- Select Create a shared feed in an empty workspace, or the + beside feed navigation. Give it a name and purpose.
- Choose its visibility. Use a restricted feed for a specific group; open feeds are available to eligible site members.
- Open Feed settings → Access to grant reader or publisher access to people or teams. If a person is missing from the list, ask them to open Catch-Up once.
Audience roles and categories help people find relevant posts. They do not grant access. Start with one feed; teams and custom audience labels are optional. Names come from Confluence when the app loads people; edit your Atlassian profile to change your name.
Share Confluence documents
On a published page you can edit, select Share to Catch-Up, choose the destination, write the announcement and publish it. More → Apps → Share to Catch-Up is another entry point. One click opens the form; publishing remains an explicit action.
A feed owner can then select Track future changes. Sharing once does not automatically turn tracking on. Existing tracking remains in place when sharing again. Manage tracked pages, attachments or label rules in Manage workspace → Sources; page tracking accepts a page link from this site.
Tracked published edits are grouped after five minutes without another edit, with a maximum grouping window of fifteen minutes. Delivery can take longer if a source is unavailable. Refresh sources checks status; it does not shorten that window. Minor-edit handling follows the tracking rule. Readers must retain source access.
Add ADR or other Markdown updates (optional)
A feed owner and repository administrator set this up together:
- In Manage workspace → Sources → Add repository updates, choose Azure DevOps or GitHub. Enter the repository ID and URL, protected branch, starting commit and selected Markdown paths. Review the recipients before confirming.
- Download the setup package (.zip). It contains the scripts, configuration, workflow and a short setup guide in their required folders. Review before replacing existing repository files. Copy the signing key separately into the provider's protected secrets; it is absent from the download.
- Follow the included guide to run initialize once, check the feed, then use resume. Select automatic publication only if you want runs on changes to the approved paths; the downloaded workflows have no schedule.
The starting commit determines which changes are eligible. Existing documents are not imported automatically. Published metadata is shared with the reviewed feed members; opening the linked document still requires repository access. Excerpts are off by default. The setup package includes the repository administrator guide; support can help with publisher questions.
Lifetime and help
An app administrator sets the number of days and archive or delete in Manage workspace → Post lifetime. The default is 60 days, then archive. Archiving keeps posts and discussion in the archive. Deletion permanently removes the affected feed data; original Confluence pages and Git files remain intact. The feed JSON export is limited and is not a complete backup or restore facility.
For access problems, contact the feed owner or source owner. For a failed repository run, check its run summary before retrying; retain successful checkpoint artifacts. Do not change the baseline just to bypass a recovery error.
Support: contact@luizperren.dev. Include the action that failed, error text and app version when available. Leave out signing keys, tokens and private document contents.