How To Send Ving Invitations From Your Company Email Domain

Want Ving invitations to come from your company’s email domain instead of vingapp.com? Your IT team can authorize Ving to send on your organization’s behalf by adding Ving-provided records to your existing domain settings.

You are not creating a new domain. You are giving Ving permission to send invitations using the domain your company already owns.

This feature has previously been called email white-labeling.

What changes when you authorize your domain?

Without domain authorization, Ving invitations normally come from ving@vingapp.com. Employees will still see the name of the administrator who assigned the training.

Once your domain is authorized, invitations can come from your organization’s email domain instead. This can make the invitation more recognizable to employees and help email providers verify that Ving has permission to send it.

Authorizing your domain can support email deliverability, but it does not guarantee that every invitation will reach the inbox. Your employees’ email providers and your organization’s security settings still determine whether a message is delivered, filtered, or sent to spam.

How does domain authorization work?

Ving will provide the DNS records your IT team needs to add to your organization’s existing domain settings.

DNS records help email providers confirm who is allowed to send email using your domain. Depending on your configuration, these records may support:

Your IT team does not need to build a new domain or give Ving access to your entire email system. They only need to add the specific records provided by Ving.

Is this email spoofing?

Email spoofing usually refers to someone using another person’s email address or domain without permission.

That is not what is happening here.

By adding the Ving-provided DNS records, your organization is explicitly giving Ving permission to send invitations using your domain. Email providers can then verify that authorization instead of treating the message as an unauthorized attempt to use your company’s identity.

What happens if the records cannot be verified?

If Ving cannot verify the required domain settings, the invitation will be sent from ving@vingapp.com instead.

This prevents an issue with your domain settings from holding up an employee’s training invitation.

Could our internal email filters still block invitations?

Yes. Some organizations have additional security rules that block messages appearing to come from the company’s domain when they are sent through an approved outside service.

If your employees are not receiving invitations after your domain has been authorized, ask your IT team to:

• Confirm that all Ving-provided DNS records are active and correct
• Review internal anti-spoofing and email-filtering rules
• Confirm that Ving is approved as an authorized sender
• Check whether Ving invitations are being quarantined or sent to spam

Ving Support can provide the information your IT team needs to review the setup.

How do we get started?

1. Contact your Ving Success Team Member or support@vingapp.com.
2. Confirm that your organization is eligible to send invitations using its domain.
3. Ving will provide the DNS records and setup information.
4. Send that information to the person or team that manages your company’s domain.
5. Your IT team will add the records to your existing DNS settings.
6. Ving will verify the records before invitations begin using your company’s domain.
7. Send a test invitation to confirm that everything is working as expected.

Need help?

If you have questions about authorizing your domain, contact support@vingapp.com or call 330-574-8022.