White labeling Requirements

Owned by Himanshu Kapoor
Last updated: Dec 22, 2020
2 min read

Email -White Labeling

  • Requirements

Credentials for Email (UserName: Password) + Host/Port of Email Server which will be used to send out the File request emails to the customer.

  • Without Email-White labeling

Without Email - White labeling , the customers will be getting email for file requests from Botdoc <postmaster@botdoc.io>.

  • With Email - White labeling

With Email - White labeling , the customers will be getting email for file requests from client’s server instead of Botdoc.

Domain - White Labeling

  • Requirements

  1. You must define which URL you want your users to receive, say suppose the domain that is going to be used is the "cloudmaveninc.com", so your document collection URL is going to be sub-domain of that. Could it be “documents.cloudmaveninc.com”. The first word of the domain indicates the sub-domain of cloudmaveninc.com

  2. Buy an SSL certificate for this domain and generate the .pfx file of the purchased certificate (using the SSL cert, bundle, and private key that was used to purchase SSL.)

  3. Go to the website where your ' cloudmaveninc.com' domain was purchased and update the DNS records. You are going to need to add a new CNAME record. 

If the sub-domain chosen in step 1 was “documents.cloudmaveninc.com"

then the following CNAME must be created:

Host: documents

Value: botdocapi-pushpull-app.azurewebsites.net

                

  • Without Domain - White labeling

 

As you can see ,without Domain - White Labeling , when you click on CLICK HERE button to upload or to download the files the URL will be of botdoc. (https://secure.botdoc.io/)

  • With Domain - White labeling

With Domain - White Labeling , when you click on CLICK HERE button to upload or to download the files, there will be client provided URL . As you can see , in the above image the URL is https://secure.habitatgsf.org/ (URL provided by the client)