JAMF is like Device Management tool used for Apple Family products.
Admin could control your apps what to use, what to block, monitor whole machine remotely using the software.
Even you are admin user for that Mac, JAMF still controlled with constraints to use default applications.
Ref:
https://apps.apple.com/us/app/testflight/
Test Flight used for BETA testing of your app before App Store submission.
It will be uploaded from Xcode using the Distribution Profile. It will go Apple review, turn around time will take min 2days for First Version upload, subsequent build no. increase will be auto approved sooner. Any further increase in version will take 2 days for sure.
(E.g) 1. 0 (1) - 2days
1.0 (3), (4), .. will be quicker
1.1 / 2.0 … will take time for review.
Any uploaded Builds will go auto expire for Build Shared in the Test Flight 90days (as on). But caveat is, those who downloaded and using the build will not break, it will still work without issue. Any new builds posted will give Notifications to the user, but not force to upgrade from TestFlight.
If we are plan to force upgrade, we need to right the logic in the Service on launch and alert the user for upgrade, no other choice with Expiry build with test flight.
Above are experience with my project.
