On-boarding and Account FAQs

Products

• Endpoint Protection Mobile

Issue/Introduction

On-boarding and Account FAQs

Resolution

How is an Appthority MTP instance created?

You work with your Customer Success Manager, who works with an Appthority Administrator to provision your account. This includes the Cloud and MTP Manager, user accounts, and one or more Organizations (your workspace).  

Are there any minimum requirements to get started with Appthority?

The EMM Connector has requirements based on the EMM. See the Help documentation for your EMM.

What personnel are needed for the implementation?

The following roles need to be filled in support of an Appthority MTP implementation:

• Appthority Customer Success Manager
• Appthority Administrator (internal to Appthority)
• Organization Admin - at least one user, with EMM Admin privileges, who can set up the EMM integration  
• For an on-premises deployment: a Systems Admin who manages VMs or Docker containers for your company
• Optional: Policy Admin - at least one user who will work with Threat Indicators and policies on an ongoing basis. Ideally this person also has EMM Admin privileges. An Org Admin can fulfill the same role.

In the Help see Prepare for EMM Integration.  

What is the privacy policy for personally identifiable information in Appthority?

An EMM integration can be configured to not allow MTP Manager to display personally identifiable information (PII) including names, email addresses, and phone numbers. Otherwise this information is displayed in the Devices tab. 

Some device identification information is stored in MTP Cloud but hashed into an Appthority Device ID for display in the MTP Manager Devices and Device Details tabs.  

In the Help see Data Collection and Storage and About the Devices Tab.

Here is the official privacy policy.