Where do my Critical Path email reminders go?
Your reminder destination is your account or workspace member email. The support address is the sender and reply-to.
Your reminder destination
Critical Path addresses your own reminders to your sign-in email. A team member’s reminders use that member’s workspace email. support@quadrant.works may appear as the sender or reply-to address; that does not mean it received the reminder.
Check a test reminder
1. In Critical Path, open Settings → Connections and read the managed email destination.
2. Send a test to your own sign-in address.
3. Check that inbox, spam, and any company quarantine. Open the message details and verify the To address.
4. If the destination is wrong, check your sign-in identity and the member email saved in your workspace before changing routing.
A provider “accepted” result confirms that the email was submitted for delivery. Confirm arrival in the intended inbox before relying on reminders. If you still need help, email support@quadrant.works with the approximate send time and time zone, your expected destination, and the test result. Do not send passwords or tokens.
Critical Path addresses your own reminders to your sign-in email. A team member’s reminders use that member’s workspace email. support@quadrant.works may appear as the sender or reply-to address; that does not mean it received the reminder.
Check a test reminder
1. In Critical Path, open Settings → Connections and read the managed email destination.
2. Send a test to your own sign-in address.
3. Check that inbox, spam, and any company quarantine. Open the message details and verify the To address.
4. If the destination is wrong, check your sign-in identity and the member email saved in your workspace before changing routing.
A provider “accepted” result confirms that the email was submitted for delivery. Confirm arrival in the intended inbox before relying on reminders. If you still need help, email support@quadrant.works with the approximate send time and time zone, your expected destination, and the test result. Do not send passwords or tokens.