Platform Creation Tasks
      Back to home
      1. Help Center | Knowledge Base
      2. Enterprise Solution
      3. Platform Creation Tasks

      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. What and who is Coviu?
      2. Creation of the custom URL (DNS entries).
      3. Creation of your email sending address and email forwarding (DNS entries).
      4. Creation of your SMS Short Sender Code.
      5. SSO - Which SSO systems do we integrate with?
      6. Firewall - What are the Firewall requirements?
      7. Are there any desktop requirements?
      8. Further Support

      What and who is Coviu?

      Coviu is an Australian made and owned video telehealth platform. Coviu was developed with the help of the CSIRO and eventually became a company in its own right.

      Coviu is the platform of choice for many large Australiana and international organisations including the Australian Department of Health, Defence and numerous state Government departments and universities. 

      Coviu is a Software as a Service (SaaS) platform requiring no server hardware on your behalf and we use AWS servers in Australia for management of the platform. For more information on how we handle privacy and security matters, click here.

      Read on to learn more about the IT requirements that may impact you as a new Coviu Enterprise customer.

      Creation of the custom URL (includes DNS entries).

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

      • The are are two parts to the creation of the custom URL:

        1. A decision on the name. The decision on the choice of sub-domain usually falls to the project management team. The chosen name might relate to the service e.g. telehealth or telecounseling or consultations etc. 
        2. The creation of the chosen sub-domain will usually fall to the IT team to create or edit the relevant DNS entries. This is done in conjunction with our IT engineers. 

      • We recommend a sub-domain/custom URL of a DNS zone you manage is allocated for the platform e.g telehealth.yourdomain.com

      • We provide an HTTPS certificate for the domain using AWS Certificate Manager. This requires a CNAME record in your allocated sub-domain 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.

      • The are are two parts to the creation of the email sending address:

        1. A decision on the choice of the email address. The decision on the choice of email address usually falls to the project management team. The chosen address might relate to the service e.g. telehealth@example.com or telecounseling@example.com or do-not-reply@example.com.
        2. The creation of the chosen email address will usually fall to the IT team to create or edit the relevant DNS entries. This is done in conjunction with our IT engineers. 
      •  Caveats:
        • We do not support using alternative MTAs to deliver email.

      Click here for more information.

      Creation of your SMS Short Sender Code.

      An SMS short sender code is a code you can choose to represent your company when an SMS is sent from your platform. The default is 'Coviu', but as an Enterprise customer, you can customise it to something within an 11 character range. You will need to choose one SMS short code to represent your platform.

      When would an SMS be sent?

        • There are a couple points where an SMS might be sent to a client or patient from your Coviu platform:
          • From the Waiting Area. A clinician can send your waiting area link from the platform to a client or patient via SMS.
          • From Scheduled Sessions: If a clinician uses Scheduled Sessions to book a consultation with a client or patient, a confirmation SMS is sent (providing the clinician has added the clients' mobile or cell number.)
          • From Scheduled Sessions: If reminder options have been set in Scheduled Sessions, then these can also be sent via SMS.

      How do I choose it?

        • The project team would usually decide what short code they want. It could be your company name or an abbreviation thereof. It could also be something that represents the service you are offering.
        • Your code should be 11 characters or less, including spaces. It can be a combination of letters, numerals and spaces.
        • Your Coviu Implementation Manager will ask you what you want for this code and provide the necessary documentation to register it with our telecommunications provider, Twilio, and the Australian Communications and Media Authority (ACMA).

      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
      • Auth0

      Click here for more information.

      Firewall - What are the Firewall requirements?

      See below links for our firewall port and domain whitelisting 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 enterprise-support@coviu.com.