Review and approve changes

A change is a reviewed update to a domain's authentication records. Preparing one never changes DNS.

Save and apply

If you hold the rights to prepare, approve and apply changes for the domain, you review the exact before and after, then choose Save and apply. Mailglo checks that exact version, records your approval and publishes it in one step. Pressing it again never applies the change twice. If something must change first, such as a newer version of the change or a record that changed since you prepared it, Mailglo lists the reasons and changes nothing.

After publication Mailglo verifies the result on its own: first that DNS serves the new record, then what the next reports show. The change page says which stage it is at: published, DNS verification pending, failed, or an outcome Mailglo could not confirm, which you reconcile from the served records. A published record shows the configuration; reports show how mail fares.

When your DNS is managed at your own provider, the button reads Save and show the record to publish. Mailglo shows the exact record to add there; you report when it is published and Mailglo checks it.

The steps

1. Prepare: choose the kind of change and say why. Mailglo shows the exact record before and after, the services affected and how to undo it.
2. Check: Mailglo validates the result, including SPF's ten-lookup limit and DMARC syntax.
3. Approve: a person with approval rights approves that exact version, or an agent does under a standing policy (see below). If the change is edited, it needs approval again.
4. Apply: for hosted records Mailglo publishes the change. Otherwise you publish the record it shows you, then report that you have.
5. Verify: Mailglo reads the published record at your domain's nameservers and checks the next reports before marking the change done.

Who may do what

Preparing, approving and applying are three separate permissions. Save and apply is offered only to a person who holds all three for the domain; anyone else sees the steps their permissions allow, and the change waits for the next person. An agent can prepare changes. It approves one only under a standing policy that a person created for that client and kind of change; a change that raises DMARC enforcement always needs a person. Save and apply is a person's action, so an agent uses the separate steps.