There is not a native, customer facing functionality for tracking the sending of notifications, subscriptions and reminders. What we typically recommend if there is a need for auditing of email notifications is that a notification that needs to be monitored be copied with all the same triggering criteria and sent to the Admin who is responsible for keeping an on on that, or that they are included in the list of users being notified.
Additionally for those who are having issues with a specific user who might not be receiving emails because they are being rejected or delayed if you put in a support case as an application or account admin with the specific email address needing to be checked we can check with our email provider to see if email notifications going to that user are being rejected or delayed. That can just take a little turn around time as we do have to reach out to their logs. I hope this information is helpful.
Thank you both for your insight. Our internal auditing department wants us to prove on a quarterly basis that emails are getting sent by Quick Base to the intended recipients. Since we cannot prove it yet - other than showing where in Quick Base we TELL the system to send the emails to particular addresses, the admin is having to manually send out all emails so that she has a paper-trail to show the auditing team. I am trying to find her a solution in Quick Base so that she can take advantage of Quick Base automation.
How were you able to get yourself specifically "cc'd" instead of notified as the "To"? I thought that if the admin received an email that specifically displayed his email address as the "CC:", then it would also naturally also show the "TO" recipient email address - and that might meet my auditors requirements.
If you are sending the email as the result of a button / hyperlink click some of the API methods take an argument for multiple recipients and if not you could through script send two emails in succession (although this would provide less proof).
The second approach is more fun but there probably is some combination of features or services where you can bounce the email to multiple recipients. It is just an effort in discovery and experimentation.
Okay, thank you very much for the suggestions. I will need to look into these options...
Is there a way to have a field formulaically triggered from something in the backend that doesn't happen unless Quick Base has done something such as sent an email? Long-shot - but I thought I would try and ask....