Portals are the landing page that visitors see when they connect to your Wi-Fi. There are situations where you want a different portal for a specific location. Maybe your company has a temporary event or maybe you want a different authentication method for your locations. You'll have to change your portal for that. Don't worry, we've got you covered with the following guide.
Portal template structure
First here's an example of the file structure of a basic portal
Your portal template must follow some rules to work properly:
An index.html file must be present
The login form must be in the index.html file and contain an HTML element with the source property set to the registering method. The following social network authentication providers can be used: Google, Facebook, Twitter, Linkedin, Instagram, Pinterest, and Wechat.
The user can also self-register via email, SMS or with a sponsored registration. In this case, an API call must be made.
When uploading the portal, it will be parsed to look for an HTML element with the source property set to the registering method. It must be in a form HTML element. The form element itself can have no properties, they will be added automatically when uploading the template. It is advised to define the source in a hidden input element like this:
<input type="hidden" name="source" value="self">
For more information on how to register your users, check the related documentation
Upload your portal on the administration console
To add a new portal, click on portals in the sidebar menu
fill in the fields as you need
click on upload cloud icon (arrow up) to upload your zip compressed portal and you are good to go