What happens after saving?
ACO Communications Hub keeps records in the Directory. Saving a change updates that record. Publication to another service is a separate step.
1. Review and save
When you edit a record, select “Review changes” to compare the previous and proposed values. Then select “Prepare review”. The service checks your permission and the details you submitted, and saves the exact request. Check the prepared values, then select “Apply reviewed request”.
If someone has changed the record since you opened it, your save is refused. Open the latest record and review your changes again. This prevents you from replacing another person's changes without seeing them.
2. The central record changes
When an Editor or Admin applies a reviewed request, the Directory changes immediately. There is no separate approval step for them. The system records who made the change and gives it a change reference and a revision number.
A Contributor's save is different. It is submitted as a proposal and changes nothing in the Directory. An Editor or Admin must approve it in “Directory approvals”. Contributors can follow their proposals in “My submitted changes”.
3. The public Directory updates
Applicable public changes are sent to the Members Directory on anglicancommunion.org. Only information included in the public directory is published. A saved field does not necessarily appear on a public page.
The publication service checks for waiting changes every minute. It builds the directory update, publishes it, and checks the result. Publication can take longer than a minute. A successful save does not mean the public page has already changed.
4. Check the result
Use “Change history” or “View change status” in ACO Communications Hub to see whether the change was saved and whether publication succeeded. If the save response is lost, check that change's status before submitting another change.
If publication fails, the saved central record remains in place. The service retries publication. If a problem remains, give the change reference to the service administrator. An independent monitoring service, separate from the Directory, checks each published change against the signed release and reports its verdict on the change page and under “Connected services”. When that service cannot be reached, verification is shown as unavailable, never as success.
Correcting a mistake
Open a saved change in “Change history” and select “Restore previous values”. Review the values, prepare the review, then select “Apply reviewed request” to save a new correction. The original change and the correction both remain in the history. Publication follows the same process as any other save.
Restoration is available only when the record has not changed again since that save. If it has, open the latest record and review it before making a correction. A change made by someone else while you review a restoration also prevents the restoration from saving. If the change includes a field that only an Admin can edit, ask an Admin to restore it.
Which services receive changes now?
The Directory supplies the live Members Directory on anglicancommunion.org. Cycle of Prayer delivery remains password-protected on www.anglicancommunion.org.
The Cycle of Prayer checks for church and diocese updates each hour. It publishes applicable details for churches already in the schedule, then checks the website. Existing prayer dates remain unchanged. A new diocese, an inactive church, or a change between Sunday and weekday prayers needs an editorial decision before the schedule can change.
Use “Connected services” in ACO Communications Hub to see the last verified Cycle publication and any pending decisions. Publication and verification can take longer than one poll. Check the receipt before treating an update as published.
Person contact fields do not appear in the Cycle of Prayer church feed. A person-contact change does not change a prayer entry.
The Directory also maintains eligible successor Bishops’ Hub profiles and the intended Bishops Hub Updates mailing list. Member sign-in and email from the successor Hub remain off. Editing a Directory email address does not silently change an existing Hub login address. Mailing changes follow the recorded consent and provider restrictions.