White Label Portal - Portal Management

Note : This article applies to customers that have a Professional or better account.

White Label Portals allow you to brand our service as your own. You can create users, assign permissions and privileges, track page views, add sites, and create your own custom pages (remotely loaded) inside the portal.

This article explains how to setup your custom portal.

 

1) From the left hand navigation click the 'Portal' icon (the globe) and select 'Manage Portal'.

 

2) Complete the basic information fields for the portal.

Portal Name displays as the heading at the top of the page on Login, Logout and Password Reset pages, and as the first part of the page title on all other pages.

Sub Domain will usually be your company name.

We'll send any support email requests to your nominated support email address and we'll send all portal emails (password reminders etc..) from this address. To ensure smooth email delivery consider setting up SPF an DKIM for Postmark.

Shared Key is used when adding additional pages to your web portal. We'll cover the main uses of this below in fe moments.

Portal images allow you to set a Logo and a Favicon.

 

3) Define your color scheme and optionally add any CSS, Javascript or HTML into your page header or footer.

Note : The header and footer code boxes allow for any HTML input. Invalid html can mess up your portal web pages so do take care. 

4) Optionally add any pages to your portal. 

Page Title becomes the browser title of the page and the page heading.

Navigation Title becomes the link to the page on the main menu.

Page and menu icon becomes the icon in the page navigation and the icon next to the heading at the top of the page.

Code is HTML which is imbedded in the page. It can be an iFrame, Javascript to remotely load a page, or plain old vanilla html itself.

Here is an example of a basic page setup.

Which in your portal produces a page like this :

You can also use Substitution variables in portal pages. The variables are {{authtoken}}, {{email}} and {{role}}. {{authtoken}} imbeds user information in the code which can securely identify the logged in user to your application/pages. {{email}} places the email address of the logged in user in your code. {{role}} imbeds the user's role in your code. Variables are URL encoded, ready for use in URLs.

For example : In this instance we're remote loading a page from starport.net. The page code is :

<div id="superpage"></div>
<script>
$('#superpage').load('https://www.starport.net/index.php?{{authtoken}}');
</script>

The resulting page on the portal looks like this :

Note : Your remote server needs to set the 'Access-Control-Allow-Origin: *' HTTP header, which is a simple one line of code in most programming languages.

One more quick note on the {{authtoken}} substitution variable. The authtoken looks like this : email=robjones%40teleport.com.au&nonce=1439782663&hash=16946a2d78892ca74e26b2326cf1de49

Its an email address, a nonce and a hash. The hash is an MD5 of the email address, nonce and the shared secret. Like this :md5($email . $nonce . $secret). You can use this to verify users before granting access to any secure pages.

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk