A 32GB iPad gives 10GB to the system and 8GB to apps. Everything else is divided between your users.
That single arithmetic fact decides most Shared iPad deployments. How many people can sign in without waiting, whether their photos sync, and how often somebody gets a slow first login, all follow from how you divide what is left. Apple publishes the numbers, and most deployments never do the sum.
- 32 GBMinimum device storage, and supervised
- 10 + 8 GBSystem and apps before any user quota
- 1 GBMinimum per user, with a photos consequence
- Oldest firstWhose local data is removed when space runs out
Eight things that decide whether a shared iPad feels fast or frustrating.
The storage arithmetic, which decides almost everything
Devices need at least 32 GB of storage and must be supervised. On a 32GB device, 10GB goes to the system and 8GB to apps and media. The remaining storage is divided among the number of defined users, with a 1GB minimum per user. Everything else in the design flows from what that leaves you.
How many users you can cache locally
Apple recommends setting the maximum storage value for users as low as possible, to maximise the number of cached users, minimise communication with iCloud and provide a faster sign-in experience. The trade is direct: smaller quota means more people sign in quickly, larger quota means fewer do.
The consequence of going to the 1GB floor
Apple states it plainly: photos will not sync with a Managed Apple Account for quotas of 1GB, and 1GB should only be used as a minimum when necessary. If the workflow involves the camera, that single line rules out the smallest quota, and it is much better discovered at design time than in a classroom.
What happens when the device runs out of room
If additional space is needed for a new user, the local data for the oldest user is removed. That is graceful behaviour and it is also the mechanism behind the complaint that someone had a slow sign-in this morning: their data was evicted, so their next sign-in has to fetch it again.
Managed Apple Accounts, issued by the organisation
Shared iPad requires a device management service and Managed Apple Accounts for user sign-in. Those accounts are issued and owned by the organisation rather than by the individual, which is the whole point: identity belongs to the institution and follows the person across whichever device they pick up.
Temporary sessions, and what they deliberately cannot do
Temporary sessions need no Managed Apple Account, and when a guest logs out all their data including browsing history is deleted. In a temporary session users cannot modify account settings or sign into Apple services, and purchased books cannot be assigned. With iPadOS 17 or later, the QuotaSize key can reserve space for these sessions.
Which iPads actually qualify
Shared iPad is supported on iPad Pro across all models, iPad 5th generation and later, iPad Air 2 and later, and iPad mini 4th generation and later. Estates assembled over several years usually contain something older, and finding those before the rollout is a great deal easier than after.
Supervision, and the deployment path that gets you there
Devices must be supervised, which shapes how they are enrolled and whether existing devices can be brought in without being wiped. For an estate already in service, that is the constraint that determines the project shape rather than anything about Shared iPad itself.
On a 32GB iPad, only 14GB is left to divide between all your users.
Apple publishes the allocation: 10GB for the system, 8GB for apps and media, and the remainder divided among the number of defined users with a 1GB minimum each.
- Fourteen gigabytes at a 1GB quota is fourteen cached users, and Apple warns that photos will not sync with a Managed Apple Account at a 1GB quota, and that 1GB should only be used as a minimum when necessary. If cameras are part of the workflow, that option is gone.
- At a more usable quota the number of cached users falls proportionally, and every user beyond that number gets a slower sign-in because their data has to be fetched rather than found locally. That is the whole user experience question in one line.
- When capacity is needed for a new user, the local data for the oldest user is removed. So a device shared by more people than it can cache does not fail, it simply cycles, and somebody gets the slow sign-in every session.
- The practical consequence is that device storage capacity is a design input rather than a procurement afterthought. Ordering higher capacity iPads for the rooms with the most users is far cheaper than discovering the constraint after deployment and living with it for the life of the fleet.
Four things that make a shared fleet work in practice.
We size the device before we configure it
A 32GB iPad allocates 10GB to the system and 8GB to apps and media, leaving the remainder to divide among defined users at a 1GB minimum each. Doing that sum against the actual number of people sharing each device frequently changes the procurement specification, which is the cheapest moment to change it.
We check the photos constraint against the workflow
Apple states that photos will not sync with a Managed Apple Account for quotas of 1GB, and that 1GB should be used only when necessary. Where a camera is part of what people do on these devices, that removes the smallest quota from consideration entirely and changes the capacity requirement upward.
We tune quota against cached users deliberately
Apple recommends the maximum storage value be as low as possible to maximise cached users, minimise iCloud communication and speed sign-in. That is a genuine trade rather than a setting with a right answer, and it should be made against how many people actually share the device.
We prepare people for the eviction behaviour
When space is needed for a new user, the local data for the oldest user is removed, so that person gets a slower sign-in next time. That is documented, correct behaviour and it generates support tickets from people who have not been told. A paragraph of staff guidance prevents most of them.
Four phases across roughly four to six weeks.
- 01Week 1
Size the fleet against real user numbers
How many people share each device, what their workflow needs, and therefore what quota each user requires. Then the arithmetic against device capacity, which frequently changes the procurement specification before anything is ordered.
- Users per device established per location
- Required quota per user determined by workflow
- Device capacity requirement calculated, not assumed
- Existing devices checked against supported models
- 02Week 2
Accounts, supervision and enrolment design
Managed Apple Accounts issued and owned by the organisation, their lifecycle agreed, and the supervision path decided. For devices already in service, whether they can be brought into supervision without a wipe is what determines the shape of the rollout.
- Managed Apple Account provisioning and lifecycle agreed
- Supervision and enrolment path confirmed
- Session model chosen per device group
- Restrictions and payloads defined
- 03Weeks 3 to 4
Build, pilot and measure the sign-in experience
Configuration applied to a pilot fleet in a real room with real users, and the sign-in experience actually observed rather than assumed. If people are hitting slow sign-ins, the quota or the capacity is wrong and it is far cheaper to learn that now.
- Pilot fleet configured and deployed
- Sign-in experience observed with real user numbers
- Quota adjusted based on observation
- Application and content delivery validated
- 04Weeks 5 to 6
Roll out and hand over
Full deployment, staff guidance for the behaviours that generate questions, and a support runbook covering the two things that always get raised: a slow sign-in, and a user whose data appears to have gone. Both have documented explanations and both alarm people who have not heard them.
- Full fleet deployed
- Staff guidance issued
- Support runbook covering caching behaviour
- Ongoing account lifecycle process handed over
Six UAE settings where shared iPads are the right architecture.
A school with class sets rather than one device per pupil
The original use case and still the clearest. Each pupil signs in with a Managed Apple Account issued by the school, their work follows them across devices, and intelligent caching returns them to an iPad they previously used. Sizing matters most here because class sizes are known and fixed.
A clinic with devices at shared workstations
Where clinical staff rotate through the same devices across shifts, individual sign-in gives a record of who used what and keeps each person data separate. The number of staff per device is usually higher than in education, which pushes the capacity requirement up accordingly.
A retailer with shop floor devices across shifts
Staff turnover and shift patterns make a communal login tempting and a poor idea. Shared iPad gives per-person sign-in without a device each, and temporary sessions cover seasonal staff who will not be there long enough to justify an account.
An operator with devices at fixed stations
Where a device belongs to a location rather than a person and several people use it across a rotation, the requirement is identity without device assignment. Sizing here is straightforward because the rotation is known, and the eviction behaviour is the detail to communicate to shift leads.
An organisation running iPads for visitors and events
Temporary sessions fit exactly: no Managed Apple Account needed, and when a guest logs out all their data including browsing history is deleted. The constraint to know is that purchased books cannot be assigned in a temporary session, which occasionally matters for content-led events.
A business replacing a shared generic login
Where devices currently use one account everybody knows, moving to Shared iPad restores individual identity and data separation without buying a device per person. It also gives an answer to who used this device, which is usually the question that prompted the project.
How UAE organisations deploy shared iPads.
| Feature | Shared iPad, sized properly | Shared iPad, quota guessed | One generic login for everyone |
|---|---|---|---|
Individual identity per user | Yes | Yes | No |
Data separation between users | Yes | Yes | No |
Sign-in speed for regular users | Fast, cached | Frequently slow | Instant, no separation |
Photos sync | If quota allows | Not at 1GB | Shared with everyone |
Device capacity matched to users | Calculated | Assumed | Not applicable |
Guest and visitor handling | Temporary sessions | Same as everyone | Same as everyone |
Data removed at logout for guests | Yes | Yes | No |
Who used the device is knowable | Yes | Yes | No |
Support burden | Low | Recurring sign-in complaints | Low until an incident |
Fixable without new hardware | Yes | Sometimes not | Not applicable |
Managed Apple Account sessions against temporary sessions.
| Consideration | Managed Apple Account session | Temporary session | |
|---|---|---|---|
| Account required | Managed Apple Account, org issued | None required | |
| Data persistence | Cached locally and synced | Deleted at logout, including browsing history | |
| Account settings | Available to the user | Cannot be modified | |
| Signing into Apple services | Supported | Not available | |
| Purchased books | Can be assigned | Cannot be assigned in a temporary session | |
| Storage reservation | User quota from the divided remainder | QuotaSize key on iPadOS 17 or later | |
| Sign-in speed | Fast when cached, slower when evicted | Consistent, nothing to restore | |
| Best for | Named users returning to the same devices | Visitors, casual use, high turnover | |
| Provisioning effort | Account creation and lifecycle | Minimal | |
| Audit trail of who used it | Identified user | No individual identity |
Five steps, and the first one is arithmetic.
- 1
Establish users per device and required quota
How many people share each device in each location, and what their workflow needs. If the camera is part of it, the 1GB quota is unavailable because photos will not sync with a Managed Apple Account at that quota, which raises the capacity requirement immediately.
- 2
Calculate against device capacity
A 32GB device leaves the remainder after 10GB of system and 8GB of apps and media to divide among defined users. Running that calculation tells you either the capacity to buy or the quota you can afford, and it is far better done before procurement than after.
- 3
Confirm eligibility and supervision path
Supported models are iPad Pro across all models, iPad 5th generation and later, iPad Air 2 and later and iPad mini 4th generation and later, and devices must be supervised. For devices already in service, the supervision route determines whether this is a configuration change or a re-provisioning project.
- 4
Configure accounts, sessions and content
Managed Apple Accounts issued and owned by the organisation with a lifecycle process, session model chosen per device group, restrictions applied, and applications and content delivered. Temporary sessions configured where visitors or high turnover make accounts unnecessary.
- 5
Pilot with real numbers, then roll out
A pilot in an actual room with the actual number of users, with the sign-in experience observed rather than assumed. Quota adjusted on what is seen, then full rollout with staff guidance covering caching behaviour so the predictable questions do not become tickets.
What organisations ask about Shared iPad.
Fifteen questions the sizing depends on.
Sizing
- How many people share each device?Per room, not on average.
- Do users take photos or video?Photos will not sync at a 1GB quota.
- What quota does the workflow need?Then divide the remainder.
- Is 32GB actually enough for that?Only 14GB remains to divide.
- Which rooms have the most users?They may need larger devices.
Eligibility
- Are all devices supported models?iPad Pro, iPad 5th gen+, Air 2+, mini 4th gen+.
- Are the devices supervised?Required for Shared iPad.
- Can existing devices be supervised without a wipe?It changes the project shape.
- Do we have a device management service?Required.
- Are Managed Apple Accounts in place?Issued and owned by the organisation.
Experience
- Which rooms suit temporary sessions?No account needed, nothing persists.
- Do any workflows need purchased books?Not assignable in temporary sessions.
- Are we on iPadOS 17 or later?Needed for the QuotaSize key.
- Who explains slow sign-ins to staff?It is caching, not a fault.
- What is the account lifecycle process?Joiners and leavers.
Take 18GB off your device capacity, then divide what is left by your users.
Ten for the system, eight for apps and media. Whatever remains is what each person gets. If that number is uncomfortable, the fix is device capacity, and it is far cheaper to decide that before the order goes in.
Related Services
Explore more solutions that work great with this service
iPhone and iPad Management
Remove company data from a phone you do not own
Apple School Manager UAE
The account layer under every school Apple deployment
Zero-Touch Deployment UAE
Sealed box to working device without IT touching it
Apple Device Management
Mac and iPhone fleets, encryption, patching and the September cycle
Device Enrolment
Which path, which reset, and what you can enforce after
Jamf School UAE
Apple device management built for schools and classrooms
macOS Management Dubai
FileVault, admin rights, updates and the Rosetta deadline
Jamf Pro UAE
The specialist Apple management platform, and when it earns its place