You can configure Octoboard to run completely white-labelled. This Knowledge Base post describes our white-label options.
When creating and sending reports to your customers or team members, you can set them up so that they do not contain any standard headers, footers, report images or Octoboard email messages. This configuration is done in the "Reports > White label" panel shown below:
You can have different configurations per report. When you create a new report, the configuration that you configured previously (or the default one) will be applied.
If you would like to send the reports automatically, you can configure the emails to be sent from octoboard.com or from your own domain. There are four options that you can use to configure email domains. Follow the links below to find out more about each alternative:
Once you have configured your email sending mechanism, you can then modify default email templates that are used for many different email types: connection failure notifications, end-user invitations, automated AI insights, password reset messages and others.
Read the following tutorial to find out more about different template types and how to configure them.
Email templates and the email sending mechanism are configured once for your account.
If you set up your white label client portal, all URL links in your email messages will be changed to point to your domain. Make sure that you have your CNAME configuration functional at all times, or your recipients will not be able to click on the URL links inside your emails. The white label client portal is discussed in the following section.
The white-label client portal is a great way to offer access to data visualisation features to your clients and team members. When the portal is configured, you will have a portal login screen with your domain URL, your brand colours and in your language. All Octoboard links in email communication and within the application will lead to your domain but will still be provided by Octoboard. For users who login with Viewer role, all references to Octoboard will be removed from the application.
You only need to configure the client portal once for your whole Octoboard account. The portal will offer a subdomain URL such as https://portal.yourdomain.com. Your end customers or team members could then log in and access the dashboards and reports.
There are many ways to share your Octoboard data views with end clients and team members. They are all discussed in the following tutorial. Two of the options – shared dashboards and white label client portals can make use of the custom branding feature discussed here.
Branding options are configured once per Octoboard organisation or client and are accessible from the Left Menu > Clients > Branding:
To set it for a shared dashboard, make sure you use the option when making a dashboard shared:
Are there any limitations with white label options?
When you are creating connections to cloud platforms such as Facebook or Google, you will see a popup screen that will display our application name – Octoboard. We cannot modify this name as it is a requirement from Facebook, Google and other systems that insist that the end customer should know what application is using their data API. This is why we recommend that you invite your end customers as Viewers. Viewers cannot create new connections and will not see the connection windows with the Octoboard brand.
Our support link at the bottom left of the screen will be disabled when Viewers are accessing the application through the portal login. This is because support tickets require the use of the Octoboard domain. The support link will be visible if you are accessing the platform from the Octoboard domain.
When using email sending options such as SMTP, sending of the emails may fail if your SMTP login details change. If this happens, we will send your administrator an email notification from the octoboard.com domain.
If you use to much email sending too quickly (if your email box is not "warmed up" yet), email services such as Google may block your emails sent from a custom SMTP server.