Understanding Email Address Requirements for Site Quality Monitoring*

Thanks for this  Site Quality Monitoring. It is indeed a tool long overdue and most welcomed.

However, to provide a more streamlined and user-friendly experience, there is the need to bring these an issue we ran into, to your attention. 

There is a need for clarity regarding the email address requirement for Site Quality Monitoring within a cPanel account. Specifically, it's not currently specified that the email address used must be associated with an existing domain in the cPanel.

Potential Issue with Monitoring Multiple cPanel Accounts:

What if a company operates multiple cPanel accounts but intends to use a single email address (which ought to be a common and logical approach) for Site Quality Monitoring across all? This seems to encounter issues, as highlighted by the error message received when attempting to resend an activation code using the same email address:

Error: Failed to resend the activation code with the following error: The response to the HTTP (Hypertext Transfer Protocol) “” request from “https://auth.koalityengine.com/v1/cpanel/auth/session” indicated an error (404, Not Found): {"status":"failure","message":"No user with team id (threeSixtyId) \u00******7377w7e7ed******\u0022 found.","data":null}

Yes, it can be redone with `reset_config` but allowing users to use any email might be better.

Cancellation Functionality Issue:
The 'Cancel' function as it is, is not working as expected during the process. This issue prevents users from stepping back to reinitialize the process easily.

Moving Forward:
To improve this experience, perhaps users should be informed about these specific requirements and limitations before they begin entering their email addresses for Site Quality Monitoring. This upfront communication will help prevent confusion and ensure a smoother setup process.

There's also a lack of clear guidance or a direct link to increase the count or add additional websites. To add more websites for monitoring, typically, users would be able to do that in their Site Quality Monitoring dashboard. However, it appears this option might not be visibly accessible or straightforward in our current interface.

These will make this great feature even more useful.