As an introduction to Applivery’s App Distribution, 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.
Workspace #
A Workspace is the organizational environment where all apps, builds, collaborators, store employees, and configurations are managed.
Each workspace operates independently and contains its own distribution structure and access control settings.
App #
You can understand an App as the equivalent of your project.
It acts as a container for all related builds of the same application, regardless of version or platform (iOS, Android, Windows, or custom).
Each app centralizes version management, distribution settings, and publication controls.
Build #
.ipa(iOS)..pkg,.dmg(maOS)..apk,.aab(Android)..msi,.exe,.msix,.appx,.msixbundle,.appxbundle(Windows).
Publication #
A Publication determines how and to whom a build is made available.
Publications allow administrators to control:
- Which build is distributed.
- Which Store employees or audiences can access it.
- Visibility rules within the Enterprise Store.
This enables flexible distribution strategies such as internal rollouts, department-based releases, or beta testing scenarios.
Collaborators and Store employees #
There are two different types of users in Applivery:
- Collaborators are users who have access to the Applivery Dashboard. They can be assigned different roles and permission levels, such as administrative access or development permissions. Collaborators manage apps, upload builds, configure distribution settings, and control publications.
- Store employees represent each end-user who access applications through the Enterprise Store.They do not have access to the Dashboard. Their interaction is limited to downloading and installing the applications made available to them.
Groups #
A Group is a logical collection of employees within a workspace.
Groups are used to organize users based on criteria such as department, role, location, or project. They simplify application distribution by allowing administrators to assign publications to multiple users at once instead of managing access individually.
Groups help maintain scalable and structured distribution workflows, especially in large organizations where app availability must be segmented across different teams or business units.
User Audiences #
A User Audience is a dynamic group of employees automatically generated based on predefined rules or attributes.
Unlike static Groups, which require manual user assignment, User Audiences update automatically when employees meet the defined criteria (such as department, role, location, or custom attributes).
This dynamic behavior enables scalable and automated distribution strategies. When publishing an app to a User Audience, any employee who matches the conditions will automatically gain (or lose) access as their attributes change.
User Audiences are ideal for large organizations that require rule-based, continuously updated targeting without manual maintenance.
Enterprise Store #
The Enterprise Store is your organization’s private app store.
It is a web-based portal where employees can access and download the applications published for them. The store supports branding customization, security configurations, and audience-based visibility rules.
Integration API #
The Integration API allows organizations to programmatically interact with Applivery’s App Distribution environment.
Through the API, external systems such as CI/CD pipelines, internal portals, or third-party platforms can automate actions including uploading new builds or creating or updating publications.
The Integration API enables full automation of app lifecycle processes, reducing manual intervention and ensuring seamless integration with existing enterprise systems.
App Token #
An App Token is a secure authentication credential used to authorize requests to the Integration API.
Each token is generated within the workspace and linked to a specific App or scope. It allows external systems to securely upload builds or perform automated distribution actions without requiring full dashboard access.
App Tokens should be stored securely and managed following best practices for credential protection, as they grant programmatic access to app-related operations.
App Distribution is designed for distributing applications to users, regardless of whether their devices are managed.
It can operate independently or be combined with Device Management for more advanced scenarios such as silent installations, policy enforcement, or automated deployments.