Enterprise - For Your IT Manager

This article summarises the standard IT offering when configuring a Coviu Enterprise platform.

Last Updated: Sept 2022

  • Who and what is this article for?
    • This article applies to Coviu customers who have purchased an Enterprise Coviu platform.
    • This article should be shared with your IT Manager to ensure that our offering matches your technology.
    • This article outlines the 5 areas where this implementation may impact your IT team or infrastructure.

On This Page:

  1. Creation of your subdomain (DNS entries).
  2. Creation of your email sending address and email forwarding (DNS entries).
  3. SSO - Which SSO systems do we integrate with?
  4. Firewall - What are the Firewall requirements?
  5. Are there any desktop requirements?
  6. Further Support

Creation of your sub-domain requirements (includes DNS entries).

Note: Do not create the subdomain until our engineer has signalled to do so! 

  • We recommend a subdomain of a DNS zone you manage, like telehealth.yourdomain.com, is allocated for the platform.

  • We provide an HTTPS certificate for the domain using AWS Certificate Manager. This requires a CNAME record in your allocated subdomain in order to authorise us to provision and renew this certificate. You may provide your own HTTPS certificate. However, AWS certificate manager is secure and will require less management overhead to maintain.

  • We require two CNAME records to be created for the platform:
    • One to forward traffic from the allocated subdomain to the Coviu hosted platform.
    • One wildcard entry for the subdomains of the allocated subdomain (ie *.). This is used for individual clinics on the platform.
  • Caveats:
    • If your DNS provider does not support wildcard entries, individual DNS records will be required for each created clinic subdomain.
    • If your allocated domain is the apex of the DNS zone, this may cause issues as CNAME records are not supported. This is not an issue for DNS providers like AWS as they support aliases for cloudfront distributions at the apex. We recommend not using a domain apex.
Click here for more information.

Creation of your email sending address and MTA forwarding (includes DNS entries).

By default, we send emails from the platform using our coviu.com or coviu.us domains however, you can provide us with your preferred email sending address.

We use Sparkpost as our mail transmission agent (MTA). Sparkpost requires a DKIM record on the sending domain to verify we are authorised to send on behalf of that domain. An 'include statement' may be required for your SPF record to allow Sparkpost. This will depend on your existing configuration.

  • Caveats:
    • We do not support using alternative MTAs to deliver email.
Click here for more information.

SSO - Which SSO systems do we integrate with?

We are able to integrate with the following SSO providers:

  • Azure SSO
  • Active Directory Federated Services
  • Okta

Click here for more information.


Firewall - What are the Firewall requirements?

See below links for our firewall requirements:


Are there any desktop/OS requirements?

  • Do you run an SOE with tight desktop security?
    • If yes, could it be that the previously mentioned firewall requirements need to be applied at the desktop level?
  • Do you run any remote desktop platforms e.g. Citrix, Remote Desktop etc?
    • If yes, what impact might that have on accessing a web-based platform and using local hardware e.g. camera, microphone etc? 
  • Do your desktop devices all have a camera, microphone and speakers?
  • Do your devices use our recommended browsers and is the browser kept up to date?

Further Support Options

Please contact the Coviu Enterprise Customer Success Manager via your project team in the first instance, or email support@coviu.com.