What is Authenticating a Domain?
Authenticating a domain in Lessonly verifies the email being sent from Lessonly is in fact, being sent from Lessonly.
When a user with assigning permissions assigns out content, the learner receives an email notification as if it came from the assignor's email address. Depending on the company's email settings, these messages may be treated as spam since they originate from Lessonly, not the assignor's own computer. This is a common problem for applications sending email notifications.
The most commonly used email authentication standards are SPF, DKIM, and DMARC.
Why Authenticate a Domain?
If a company has reviewed the Ensuring Email Deliverability lesson, and this lesson doesn't meet the needs of their email settings they will want to take the route of authenticating their domain through Lessonly.
The Process of Authenticating a Domain
To begin the process of authenticating a domain, please reach out to Support at firstname.lastname@example.org.
A member of the Support team can then begin the process of authenticating the domain through Lessonly's email provider, Sendgrid. Lessonly needs to be provided a main point of contact during this process to ensure the authentication is verified from the customer's end.
By default, Lessonly automatically sets the DKIM to "lly." If a different DKIM is preferred, please provide a three-letter or numerical value for the Support member to input.
Once all steps have been taken on Lessonly's end, an email is sent to the point of contact with the below message:
Hi, this is the Lessonly Support team. We are trying to authenticate your domain with SendGrid, but I don't have the ability to modify your DNS records. Can you help me add these records so that I can complete the process?
The point of contact has 48 hours to confirm the DNS records or the link will expire. Once confirmed, then Lessonly Support verifies the set-up in Sendgrid and it should be all set.
If you have any other questions about this process, please reach out to Support at email@example.com.