Taking a site down
There are three ways to remove something, and they differ in what survives. Knowing which is which matters, because one of them releases your subdomain to anybody who wants it.
#The three
Action | What goes | What survives |
|---|---|---|
Discard staging | The preview only | The live site, untouched |
Remove production | The live site goes offline | The site record, its settings and its subdomain |
Delete site | Everything, immediately and permanently | Nothing. The subdomain is released |
Deleting releases the subdomain for anyone else to claim. It also clears the edge access entry and removes the Confluence space properties. It cannot be undone.
#Who can do what
Discarding a staging preview: admins and site collaborators.
Removing the production deployment: Confluence admins only.
Deleting the site: Confluence admins only.
There is a 30 second cooldown between creating or deleting sites.
#Uninstalling the app
Uninstalling Capable destroys every published site in the tenant. It starts a teardown of every site's files, every custom domain's CDN distribution and TLS certificate, and all access records. Export anything you want to keep first.
#A few things worth knowing
Removing production keeps the subdomain reserved, which is the safe way to take a site down temporarily.
A deleted site's custom domain can be slow to become reusable. See the troubleshooting page on that.
Residual records carry a 7 day grace period after an uninstall.
#Related
Offline and deleted are not the same thing.
