Control

Approval Workflows

DNS and SSL changes can always be rolled back, but the minutes in between are downtime. Approval workflows put risky operations in front of a second pair of eyes before they go live. The requester writes down what they want to change, an approver signs off, and only then is it applied.

• Gate the risky operations

  You decide which operation types need approval: a nameserver change waits for sign-off while a routine TXT record applies straight away.

• Requests carry their reasoning

  Every request states what becomes what, and why. The approver isn't left guessing.

• Approvals land in the audit log

  Who approved what is on the record, so when something goes wrong the whole chain reads backwards.