ليس لديك صلاحية الوصول إلى هذه الصفحة.
يمكن لمطوري النظام ومشرفي المنصة فقط إدارة موظفي المنصة. إذا كنت تعتقد أن هذا خطأ، فتواصل مع أحد مطوري النظام.
العودة إلى لوحة المعلوماتWhat each mobile platform is running, and which builds are refused. The latest build drives the dismissible “update available” prompt. The floor refuses older clients outright with a 426.
Loading…
Nothing has been published for this platform yet.
Do these in order: publish the build to the store and record it below, and only then set a floor beneath it. A floor at or above the newest build forces an upgrade to something nobody can install, so it is refused.
Release details
May be left empty before a listing exists — the app shows a “contact your HR administrator” fallback instead.
Minimum build (the floor)
Raising the floor is done from the command line, where a
written reason is required and a value that would brick the fleet is
refused. It locks out every employee on an older build — including one
standing at a turnstile at shift start — and we
cannot tell you how many people that is: the build number
arrives on every request and is discarded, and device_tokens
has no build column. A confirmation dialog here could not state its own
consequence, so there is none.
Lowering it can be done here, and deliberately so. Lowering only ever admits more clients, and it is the reversal path: a wrong floor locks out the fleet until someone undoes it, and doing that from a phone at 2am is the difference between two minutes and forty.
Counting would become possible by adding
last_seen_build to device_tokens — the
limitation is a choice we have not yet made, not a property of the
system.
Current reason:
Must be at or below the current floor (). Set 0 to remove it entirely.
To raise it: