Uninstalling: what is kept and what is deleted
Uninstalling Capable for Confluence keeps its Confluence custom content. Diagrams, Markdown documents, templates, saved searches and image libraries stay in your site and are there again when you reinstall.
Everything the app holds in Atlassian Forge storage and Forge SQL is deleted: approvals and their history, approval teams, calendar events, publishing and Sites history, and settings. Atlassian can restore it for up to two weeks after the uninstall; after that it is gone. Read this before you uninstall, not after.
#What happens at uninstall
Best-effort cleanup runs inside a roughly 55-second window: the site's signing key is deregistered so a reinstall is not locked out, calendar subscription feeds are revoked, and teardown of any published Sites is started (this takes about 20 minutes per site and finishes long after the uninstall). No failure blocks the uninstall and no failure is shown to the admin.
#What is kept and what is deleted
What | After uninstall |
|---|---|
Diagrams, Markdown documents, templates, saved searches, image libraries and their attachments | Kept. They are Confluence custom content and stay in your site. Reinstall and they are there again. |
The Capable Asset Store space and page attachments | Kept. |
Capable macros on pages | Stay on the pages, but do not render while the app is uninstalled. |
Approvals, approval history and approval teams | Deleted. They are held in Forge storage. |
Calendar events | Deleted. They are held in Forge SQL. |
Publishing and Sites history, settings, and anything else in Forge storage or Forge SQL | Deleted. |
Data in Capable's own service (see below) | Kept for 30 days, then deleted. |
Approvals and calendar events do not survive an uninstall. Atlassian can restore Forge storage and Forge SQL data for up to two weeks after the uninstall. If you uninstalled by mistake, contact Capable support straight away. After two weeks the data is gone for good.
#What Capable keeps for 30 days
Some data lives in Capable's own service rather than in Confluence: your Slack connection, everyone's email, Slack and Microsoft Teams opt-outs, and the record of your installation. Capable keeps it for 30 days after you uninstall, so that reinstalling by mistake, or during a trial, gives you your connections back.
When | What happens |
|---|---|
You reinstall within 30 days | Your connections and notification switches are still there. |
30 days after uninstall | A daily job deletes that data, along with the revoked calendar subscriptions. A reinstall after this means connecting Slack again, and people set their notification switches again. |
Calendar subscription feeds are revoked at uninstall and do not come back on reinstall; people subscribe again. Separately, old versions of files on published Sites expire 30 days after they are replaced or deleted, whether or not the app is installed.
#Before you uninstall
Export each calendar you want to keep with Export as iCal or Export as CSV.
Keep a record of any approval history you need for audits, and note the settings you rely on.
If you are moving to standalone Capable apps, migrate first and verify, exactly as you would coming the other way.
Remember that pages keep their Capable macros, which do not render until the app is installed again.
#A few things that catch people out
Uninstall and reinstall is not a troubleshooting step. It keeps your diagrams and documents, but deletes approvals, teams and calendar events.
Kept content is not the same as visible content. Your diagrams and documents are still in Confluence, but the macros that show them need the app.
Deleting Capable's copy of your Slack connection does not remove the app from your Slack workspace. Remove it in Slack if you want it gone there too.
#Related
Your content stays. Your approvals and events do not.
