Skip to main content

Managing Applications

Learn how to add, edit, and remove applications from the CDOT MDM system.

Adding Applications​

There are two methods to add applications to the MDM system: APK Upload and URL Input.

Method 1: APK Upload​

Upload APK files directly from your local system.

Upload Steps:

  1. Click the Add Application button

  2. Select the Upload APK option

  3. Click Choose File or drag and drop an APK file

  4. Select the APK file from your local storage

  5. System validates the file:

    • Checks file format (must be .apk)
    • Verifies file size (maximum 150MB)
    • Extracts application metadata
  6. Review the extracted application details:

    • Application name
    • Package identifier
    • Version code and name
    • Permissions required
  7. Click Confirm Upload to finalize

Upload Results:

  • Success – Application is added to the table with a success message
  • Error – Invalid file or size exceeded triggers an error message
  • Cancel – Click Cancel to close the dialog without uploading
warning

APK Upload Requirements:

  • File format: .apk only
  • Maximum size: 150MB
  • Must be a valid Android application package
  • Ensure APK is from a trusted source

Method 2: URL Input​

Add applications by providing a download URL.

URL Input Steps:

  1. Click the Add Application button

  2. Select the URL Input option

  3. Enter the application URL in the text field

  4. System validates the URL:

    • Checks URL format and accessibility
    • Verifies the URL points to a valid APK file
    • Tests download availability
  5. Click Confirm Addition

URL Input Results:

  • Success – Application is downloaded and added with a success message
  • Error – Invalid or inaccessible URL triggers an error message with details
  • Cancel – Click Cancel to close without adding
info

URL Requirements:

  • Must point directly to an APK file
  • URL must be accessible from the MDM server
  • HTTPS URLs are recommended for security
  • Firewall rules must allow outbound connections

Editing Applications​

Modify application metadata and settings.

Edit Steps:

  1. Locate the application in the table

  2. Click the Edit button for that application

  3. A dialog opens with editable fields:

    • Application name (display name)
    • Description
    • Category
    • Pre-installation status
  4. Modify the values as needed

  5. Click Save Changes

Validation:

  • All required fields must be completed
  • Name must be unique
  • Success – Changes are saved and table updates
  • Failure – Error message displays with details
tip
  • Editing application metadata doesn't affect already deployed instances. It only changes how the app appears in the MDM interface.

Deleting Applications​

Remove applications that are no longer needed.

Delete Steps:

  1. Locate the application to delete

  2. Click the Delete button

  3. A confirmation dialog appears showing:

    • Application name
    • Number of versions
    • Warning about permanent deletion
  4. Choose an option:

    • Cancel – Closes dialog without changes
    • Delete – Permanently removes the application

Delete Results:

  • Success – Application removed from table with success message
  • Failure – Error message appears if deletion fails
caution

Before Deleting:

  • Remove the application from all profiles first
  • Verify no devices are actively using the application
  • Consider archiving instead of deleting critical apps
  • Deletion removes ALL versions of the application
  • This action cannot be undone

Single Version Restriction​

If an application contains only a single version, special rules apply.

Restriction Details:

  • The Delete Version button is not available
  • Users must delete the entire application
  • This ensures applications always retain at least one active version
  • Prevents orphaned application entries

To Remove a Single-Version App:

  1. Delete the entire application (not just the version)
  2. Or add another version first, then delete the unwanted version

Best Practices​

Application Organization​

  • Use clear, descriptive names for applications
  • Maintain accurate descriptions and categories
  • Keep package identifiers consistent
  • Document custom applications thoroughly

Upload Management​

  • Test APK files before uploading
  • Use version naming conventions (e.g., 1.0.0, 1.0.1)
  • Keep APK file sizes reasonable for network efficiency
  • Maintain backup copies of uploaded APKs

Security Considerations​

  • Only upload applications from trusted sources
  • Verify APK signatures before uploading
  • Review requested permissions
  • Test applications in a sandbox environment first
  • Keep applications updated with security patches

Lifecycle Management​

  • Regularly review and update applications
  • Remove unused applications to reduce clutter
  • Maintain version history for compliance
  • Document reasons for major version changes
tip
  • This structured approach to application management ensures efficient software deployments, updates, and removals while maintaining data accuracy and consistency.