Our intuitive self-serve Portal enables users to quickly and easily create and provision Megaport services. We continually make incremental improvements to the usability of our Portal in order to provide customers with a seamless experience. One of our most recent improvements is providing the option to set up five different user roles so that organisations can separate tasks and control of their services.
When creating an account in the Portal, users are provided with measures for security and access control for their services. Two factor authentication is supported when gaining access to the Portal and our recommended app is Google Authenticator. The APIs require a valid session token to access and provision services.
This article is a short overview of the Megaport user roles and permissions. If you prefer, you can also watch our walkthrough video here.
To begin managing your users’ roles and permissions, log in to the Portal and select ‘Company’ and then ‘Manage Users’. Please note that you must have ‘Company Admin’ privileges to edit user credentials.
Select “New User” to enter the user information and role.
For existing users, you can edit the user profile and also activate and deactivate access from this page. This allows for both pre-provisioning, fast enablement, and suspension of user access to the Portal.
When creating a new Portal role, all fields are mandatory. The user email address is required for registration and to enable notifications.
The ‘Role’ option is where users are allocated their role and associated privileges. The following five roles are available.
The ‘Read Only’ role is the most restrictive role available and does not allow any changes to your Portal account or services. Please note that a user with this role can view service details which could contain information about the service that you may wish to keep secure and private.
This user role allows the user to place and approve orders, access financial data, and delete services. Users of this role should have a financial responsibility within the organisation while also understanding the consequences of their actions on services should they wish to delete or approve services. While creating services, you can see the cost of the service before deploying. Please note that it is also possible to see the cost of deployed services by selecting a service in the Portal and viewing the initial tab.
The Technical Admin role is similar to the Technical Contact role with the addition of being able to place and approve orders. Once the Portal is set up by the Company Admin, this role then allows full control of service adds, moves, and changes.
The Technical Contact role is for technical users who know how to create services but do not have the authority to place and approve orders. The Technical Contact would typically create the service and then notify the responsible user with the correct privileges to review and approve the order. The Technical Contact can also subscribe to notifications about services.
The Company Admin user has access to all user privileges including user administration, market and financial configuration, company profile, creation and deletion of services, approval of orders, and notification subscription. It is therefore advised to limit the number of Company Admin users to only those who require this level of access.