Confluence notification triggers during bulk page moves

Answer

Moving a page to another space preserves its existing watcher list. Watchers are tied to the page’s content ID, not to the source or destination space, so they remain after the move. However, Confluence does not automatically send notifications to users who only watch the destination space; they receive an alert only if they are already watching the moved page.

Confirmed facts

• Watcher list stays attached to the page during a bulk move.
• The bulk‑move UI includes a "Send email notifications" checkbox; when checked Confluence sends emails (subject to rate limits), when unchecked no emails are sent.
• Via the REST API the notify query parameter controls the same behavior (notify=true sends, false suppresses).
• Confluence’s notification engine batches or suppresses emails for bulk moves to avoid spamming, and enforces a default rate limit of roughly 50 pages per hour per user.

Steps to verify in your environment

1. Create a test page in Space A and add a few watchers (Watch → Watch this page).
2. Perform a bulk move of that page (or several pages) to Space B using the UI. Note whether the "Send email notifications" box is checked.
3. After the move, open the page and confirm the watcher list still shows the original watchers.
4. Check the email inboxes of those watchers and of Space B admins. You should see either a single summary email (if the box was checked) or no email (if unchecked).
5. Repeat the move via the REST API: POST /rest/api/content/{id}/move?destinationSpaceKey=B¬ify=false and verify that no emails are generated.
6. Review the audit log (System → Audit Log) for entries marked page.moved and look for the notify flag to confirm the setting used.

Need more info?

Does your bulk‑move operation have the Send email notifications checkbox checked or unchecked? That detail determines whether watchers receive individual emails or a single summary, and thus whether additional notification steps are required.