Getting Started with Super Admin

To get started, you'll need a Super Admin access to your portal.  You will need to request a Super Admin account if you don't already have one. 

Some important notes:

  • Each User Portal has its own dedicated URL (which you can change to your domain).  
    • Ie.
  • Each User Portal has its own link to a project on the IoT Platform
  • Each User Portal is isolated, meaning you'll need separate accounts for each.  For example, dev, test/staging and production
  • Super Admin has mandatory two-factor authentication (code will be sent to your email with each login).

Super Admin Login:

Access the login page of your portal, ie. and login with your

Super Admin account.  Enter the authentication Token.



Once you login you will notice a menu that looks similar to this.  

Manage Accounts: This is for each of the customer accounts (also referred to as Tenants).  An Account is independent of the users linked to that account.  Advanced: You can link child accounts to parent accounts if you have customers that require multi-tiers of permissions and access.

Manage Account Users: These are all the end-users of your portal.  These users are linked to one or more Accounts.  Each user is identified by their email.  Each user will have a single sign-on account.  If a user is linked to more than one Account, they can switch between their accounts once they log in.

Manage Super Admins: This is a list of all the Super Admins.  A Super Admin has access to all data and customized dashboards.  Beta: You can also create a Super User which has less permission as Super Admins.  Super User can see Accounts and Users but no access to the HTML/JS code for the customized dashboards.

Managed Devices: These are a list of devices linked to your portal from your IoT Platform.  Devices that are linked to your portal are not necessarily linked to an Account.  Devices are automated shown here.  Some User Portals may have Device Types in the menu, this is an optional feature by request.

Advanced Config: This is a configuration page to specify a wide variety of settings.  Some examples are: naming your portal, icons, logos, images, 3rd party API keys, enabling self-service, permissions, and much more.

Config Email: This is where you can customize the design of each system email to the end-user.  Some examples are new registration, password reset, credit card error, new user added or removed.  There's also support for multi-languages.

Config Dashboard: This is where you can create customized dashboard pages.  This is where the customization code will reside and where you will spend most of your time developing. 

Template Page Config: This is similar to the Config Dashboard but for fixes pages such as login, password reset.  You can customize these pages but you can not delete them.


Typically Medium One will generate some sample Customer Dashboard pages for you to see the sample code.