Getting started with Canary
Install
Install Canary on the client accounts you want watched. The consent screen asks for three read-only permissions. If you add a client later, Canary shows it as not yet covered and links you straight to the install - nothing slips through silently.
Wait for the first scan
Canary reads the expiry date on every connected account. The first pass usually finishes in a few minutes. It is common to find one or two connections already inside the warning window.
Add your domains
Email authentication and SSL checks run against public DNS and the public certificate log, so they need to know which domains to look at. Paste the domains you send email from and the domains your funnels and sites are published on.
Where alerts go
To the email of the first admin who opens Canary - one message at 14, 7 and 2 days before anything runs out, with a link to the fix. To use a different address, write to contact@jimapps.dev from the current one.
Reconnect when warned
Canary tells you which client account, which connection, and the exact date it runs out. Reconnecting is done in the client's own account - here is how. The warning clears as soon as you open Canary again.
Next
Full documentation covers the checks, schedules and permissions in detail. Anything not answered there - support.