Description


Adding the customer and users in the MPaware portal.



Requirements


As a Partner, you will need:

  • An admin level login to the portal

The Process

Overview: 


On the left menu you have the following:
My Dashboard (Your personal progress) – new updates and notifications will show there (in image, a 1 is in red meaning you have 1 unopened notification)
Newsfeed (Forum)
My Company (Your company status/progress)
Manage Clients (Partner Portal)



Step 1: Creating the Customer: 


Under Manage Clients (This is essentially your Partner Portal) > New Client 

Enter Company name and Industry and Create.



Step 2: Adding Users


There are multiple ways to create users:



1. General Manual Creation:

Ad-hoc user creation.

Add Users in the MPaware Portal - Manually


Azure Active Directory Synchronization

Azure AD allows you to simply manage the users from their Azure site. 

Add Users in the MPaware Portal - Azure Active Directory Sync


On-Premise Active Directory

If you have clients that are using On-Premise, you can utilize Active Directory to sync the MPaware Portal and simplify user management.

Add Users in the MPaware Portal - On-Premise Active Directory Sync Setup


G-Suite Directory Synchronization:
G-Suite Directory Sync allows you to simply manage your MPaware Portal users for your G-Suite clients.

Add Users in the MPaware Portal - G-Suite Directory Sync Setup


Bulk User Management via CSV Upload
If you’d prefer to manage users manually, there is an option to upload a .csv  to add, update or deactivate users inside the portal. 

Add Users in the MPaware Portal - Using Bulk Upload 



Note: Here are a list and details of the different Role Groups: 


Employee: Basic employee access

Manager: Managers get access to reporting and employee data inside the portal.

Manager Admin: Manage Admins get the ability to manage phishing campaigns as well as the bulk manage user functionality. Standard manager accounts do NOT have this functionality

Partner Administrator: Partner Administrators are the highest level. They have access to all administrative functions for all accounts within your portal.



Step 3: Editing Existing Users


After a user is created, their account details can be edited. 

Note: If certain directory sync or federated login options are enabled, some fields may not be editable within the portal 


Editing an Existing User:


1. To edit an employee, in the “Users” section, select/click the user you are editing.
2. A modal will appear with existing user data.
3. You can edit the Role, Tag, First/Last name, Email Address, Phone, and Password






4. Messages: Here you can authorize this user (only for Managers) for company positive opt-in for the weekly Micro Trainings.

5. Enable individual level access for weekly Micro Training emails to be sent to the user. 


Additional options may be available for users within your MSP’s tenant including;

6. Additional Access: 

Billing  Enables user to access billing tab of portal
Marketing Material  Enables user to access Partner Resource Kit
Payment Information  Enables the user to edit payment information
Tax Exempt  Enables user to access the Sales Tax Exemptions tab



7. Acknowledge Policies: If slider is on (green) the user has acknowledged the provided policies and procedures. You can also check or uncheck these here


Note: If synchronization methods (Azure, On-Prem, Google) are enabled, editing users manually via this method may result in an error for certain fields. The user should be edited via the appropriate sync method instructions. 


Editing User Actions: 


Actions can be performed on any or multiple users. Use the checkbox options to select the user(s) you wish to perform the action on. 

 Actions include:

  • Activating a User
  • Inactivating a User
  • Sending a Welcome Message
  • Clearing a Bounced Email 
  • Resetting a Password
  • Deleting a User
  • Resetting a Deleted User
  • Resetting MFA


Note: Using the “select all” checkbox at the top of the table will only select all the users on the current page. Performing an action for all users would need to be done on a page-by-page basis.