applivery.com

Main concepts

As an introduction to Applivery, we highly recommend you explore and understand the following basic concepts that will be explained in detail in the following chapters of the documentation since they represent the very basic concepts of our platform.

Dashboard #

The part of the platform where you and your team will administer everything related to the management and distribution of your Apps. You can find it under https://dashboard.applivery.io. Users of the Dashboard are named Collaborators of your projects and may have administration or development permissions over your projects (Apps).

Workspaces #

Workspaces represent a logical distribution of your projects (Apps and Devices). In most cases, they represent a single company and are the container of all Users, Apps, and Devices that belong to it, but in other areas, the organizations could represent different business units of the same company or even a single person/developer.

Apps #

You can understand an App as the equivalent of your project. Apps can store both iOS and Android files (IPAs, APKs, AABs). You can manage the Apps on your own and have full control over them so you’ll decide whether to create a new app or reuse an existing one when starting a new project.

Devices #

They represent each Android (phones & tablets) or Apple (iPhone, iPad, iWatch, AppleTV) device that is being managed by the platform.

Builds #

Every version of your App. They are created the moment you upload a new .ipa, .apk or .aab package to the platform.

Collaborators and Employees #

There are two different types of users in Applivery:

  • Collaborators are users that will have administrative permissions over the different entities of the platform (Apps, Devices, Users, etc). They have full or limited access to the Dashboard based on their role: Owner, Admin, Developer, and Viewer.
  • Employees represent each end-user that will have access to your Apps and Devices. You will be able to customize Employee permissions both on the App and Organization levels.

Enrollments #

Represent a placeholder for new Apple or Android devices that will be added to the platform. Enrollments contain the information needed to register a new device in Applivery and are always associated with a given User. For security reasons, Enrollments have a TTL (time to live) that ensures they are only accessible for a limited time.

MDM Users #

MDM users represent an easy way to group multiple devices. Typically, they represent a real user that owns multiple devices (either Android or Apple devices). You can manage groups on your own by defining as many users as you want or even grouping all devices under a single global user.

Google Enterprise #

An Enterprise resource binds an organization to the Android Management API. Devices and Policies both belong to an enterprise. Typically, a single enterprise resource is associated with a single organization.To start using Applivery MDM for Android you will have to bind your Applivery Organization with Google by following the guided process in the dashboard. You can start this process from Applivery MDM > Settings > Android.

Policies #

Policies (also called a policy) are the core resource of the Android Management API. You use them to create and save groups of device and app management settings for your users to apply to devices.

Updated on February 9, 2024
Was this article helpful?

On this page

— talk to an expert —

Schedule a demo