One iPad, many users, each with their own login. The whole design comes down to storage arithmetic.
One pool of iPads, individual sign-ins, whether that is a classroom, a hospital ward or a retail floor. Whether the experience feels instant or maddening comes down to arithmetic Apple has already published: on a 32GB iPad the system claims 10GB and apps and media take another 8GB, leaving only what remains to be split across every person who uses it. Almost nobody performs that calculation before raising the purchase order. We do it before anything is ordered, remotely from Gachibowli, Hyderabad, for organisations across India.
- 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 data is evicted when space runs out
Eight things that decide whether a shared iPad feels fast or frustrating.
The storage arithmetic that decides almost everything
You need supervised devices carrying at least 32 GB. Of that, the operating system takes 10GB and apps and media take 8GB before a single user is considered. Whatever survives gets divided among your defined users, and no user can hold less than 1GB. Work out that remainder first, because every subsequent decision on this page depends on the number it gives you.
How many users you can cache locally
Apple guidance is to keep the per-user storage value as low as you reasonably can, which caches more people locally, reduces chatter with iCloud and produces noticeably faster sign-ins. There is no cleverness available here, only a straight trade. Shrink the quota and more people get a quick sign-in. Grow it and fewer do.
The consequence of the 1GB floor
Apple is unambiguous that photos will not sync with a Managed Apple Account when the quota sits at 1GB, and that this floor should only be used where genuinely necessary. Now think about what your users actually do. A science practical, a site inspection, a wound photograph on a ward round. Any camera-based workflow eliminates the smallest quota outright, and that is a far better thing to learn during design than during week one.
What happens when the device runs out of room
Needing room for a new person means the local data belonging to the longest-idle user gets cleared. Their account loses nothing, so no data is destroyed, but their next sign-in is slow because everything must be retrieved again. Understand this behaviour properly, because it sits underneath very nearly every complaint we are asked to investigate.
Managed Apple Accounts, issued by the organisation
A management service plus Managed Apple Accounts are both required for people to sign in. Those accounts belong to your organisation rather than to the individual, and that ownership is precisely the point. Identity sits with the institution and travels with the person to whichever device they happen to pick up, in whichever room, on whichever floor.
Temporary sessions, and what they deliberately cannot do
No Managed Apple Account is needed for these, and everything a guest did, browsing history included, is erased the moment they sign out. The deliberate limitations are worth knowing: nobody in a temporary session can change account settings or sign into Apple services, and you cannot assign purchased books to them. On iPadOS 17 and later the QuotaSize key lets you set space aside specifically for guest use.
Which iPads actually qualify
The supported list covers every iPad Pro, iPad 5th generation onward, iPad Air 2 onward and iPad mini 4th generation onward. Any Indian fleet assembled across several procurement cycles almost certainly contains something that predates one of those lines. Identify those units during planning, because finding them mid-rollout means explaining to a department why their iPads are the ones that will not work.
Supervision, and the deployment path to it
Supervision is mandatory, which governs how devices enrol and whether iPads already in service can join without being wiped first. For hardware spread across several sites and already in daily use, that single requirement shapes the entire project far more than anything specific to this feature.
On a 32GB iPad, only 14GB is left to divide between all your users.
The allocation is published and fixed: 10GB to the system, 8GB to apps and media, and whatever survives shared among your defined users at no less than 1GB each.
- Set the quota to 1GB and fourteen gigabytes buys you fourteen cached users, but remember Apple explicit warning that photos will not sync with a Managed Apple Account at that level. Where cameras feature in the work at all, that option is gone before you begin.
- Raise the quota to something genuinely usable and your cached user count drops in direct proportion. Every person past that count experiences a slower sign-in, because their data has to be pulled down rather than found waiting on the device. The entire user experience question really is contained in that one sentence.
- Making room for a new user clears the longest-idle one. So a device shared by more people than it can hold does not break in any obvious way. It cycles quietly, and somebody sits through the slow sign-in every single session without ever understanding why.
- All of which makes storage capacity a design input rather than a procurement detail. Specifying higher-capacity iPads for your busiest rooms costs a little more once. Discovering the constraint after deployment means living with it for the entire life of the fleet, and no configuration change will rescue you.
Four things that make a shared fleet work in practice.
We size the device before we configure it
We take the published allocation, subtract it from the capacity you are considering, and divide what is left by the actual number of people sharing that device in that specific room. Run that honestly and the answer frequently changes what you should be ordering. Changing a specification before a purchase order is signed costs nothing at all.
We check the photos constraint against the workflow
Since photos will not sync at the minimum quota, we ask early whether anybody uses the camera for actual work. If they do, the smallest quota leaves the table immediately and your capacity requirement rises accordingly. This gets raised in the first week, rather than emerging months later through a teacher wondering where their pupils photographs went.
We tune quota against cached users deliberately
Apple advice to keep the storage value low maximises cached users, cuts iCloud traffic and speeds up sign-in, but it is a genuine trade-off rather than a setting with a single correct answer. So we decide it room by room, weighed against how many people genuinely share each device there, instead of applying one number across an entire estate.
Remote-first, and we prepare people for eviction behaviour
Clearing the longest-idle user to make room, and giving that person a slower sign-in next time, is documented and entirely correct behaviour. It is also guaranteed to generate tickets from anybody who was never told it happens. So we write the short staff explanation that prevents those tickets, run the whole engagement remotely from Gachibowli, Hyderabad, and support managed clients under a 30 minutes response SLA.
Four phases across roughly four to six weeks.
- 01Week 1· Week 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· Week 2
Accounts, supervision and enrolment design
Managed Apple Accounts issued and owned by the organisation with an agreed lifecycle, and the supervision path decided. For iPads already in service, whether they can be supervised without a wipe 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-4· Weeks 3-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 observed rather than assumed. If people hit 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-6· Weeks 5-6
Roll out and hand over
Full deployment, staff guidance for the behaviours that generate questions, and a support runbook covering the two things always 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 Indian settings where shared iPads are the right architecture.
A school with class sets rather than one iPad per student
This is what the feature was built for, and it remains the cleanest fit, particularly against Indian school budgets where one device per child is rarely affordable. A single class set rotates between sections, each pupil signs in with a school-issued Managed Apple Account, their work travels with them, and caching tends to return them to a device they have used before. Sizing is most critical here of all, because class sizes are known, fixed and large.
A hospital or clinic with devices at shared stations
Nursing and clinical staff cycling through the same tablets across three shifts a day need individual sign-in for two reasons: a record of who used which device when, and genuine separation of each person data. Those are precisely the questions a clinical governance review or a DPDP inquiry will put to you. Note that staff per device runs considerably higher here than in a school, which drives your capacity requirement upward.
A retail chain with shop floor devices across shifts
High turnover and rotating shifts make a single shared password extremely tempting and a genuinely poor decision. This gives you per-person sign-in without buying a device for everyone, while temporary sessions neatly handle the seasonal staff hired for the festival rush who will not be around long enough to warrant creating accounts.
A plant or warehouse with devices at fixed stations
When a tablet belongs to a workstation rather than to an individual and several operators pass through it during a rotation, what you need is identity that is not tied to hardware. Sizing here is refreshingly simple because the rotation is already documented. The one thing worth explaining to shift supervisors is the eviction behaviour, so a slow sign-in is understood rather than reported as a fault.
An organisation running iPads for visitors and events
Temporary sessions were designed for this. No account provisioning required, and everything the guest did, browsing history included, vanishes at sign-out. Carry one limitation into your planning: purchased books cannot be assigned during a temporary session, which occasionally matters for training days and content-led events where reading material is the whole point.
A business replacing a shared generic login
Right now every device shares one password that the entire department knows and nobody has changed in two years. Moving to this model restores individual identity and separated data without purchasing hardware for everyone. It also answers the question that almost certainly triggered the project: when something went wrong on that iPad, who was actually using it.
How Indian organisations deploy shared iPads today.
| 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, organisation 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
Week 1
We count the people sharing each device at each location and ask what they actually do on it. Camera work anywhere in that answer removes the minimum quota from consideration, since photos will not sync with a Managed Apple Account at that level, and your capacity requirement rises on the spot.
- 2
Calculate against device capacity
Week 1
Subtract the system and app allocations from the device capacity and divide what remains among your defined users. That one calculation produces either the capacity you should be buying or the quota you can realistically afford. Do it before the purchase order and it costs you an afternoon. Do it afterwards and it costs you the fleet.
- 3
Confirm eligibility and the supervision path
Week 2
We check your inventory against the supported model list and confirm every device is or can be supervised. Where iPads are already deployed and in daily use, the available supervision route is what determines whether you are buying a configuration change or a full re-provisioning project, and those are very different pieces of work.
- 4
Configure accounts, sessions and content
Week 2-3
Accounts get issued under your organisation ownership with a proper joiner and leaver process behind them, each device group gets whichever session model suits it, restrictions go on, and applications and content are delivered. Where visitors or heavy turnover make named accounts pointless, temporary sessions are configured instead.
- 5
Pilot with real numbers, then roll out
Week 3-6
We pilot in a real room with the real number of users rather than a comfortable subset, then watch the sign-in experience rather than assuming it, and adjust the quota based on what we actually observe. Full rollout follows, accompanied by staff guidance explaining caching behaviour so the entirely predictable questions never arrive as tickets.
What Indian organisations ask about Shared iPad.
Fifteen questions the sizing depends on.
Sizing
- How many people share each device?Per room or per shift, 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 iPads 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.
The pages around this one.
iPhone and iPad management
The wider management view for iOS and iPadOS fleets, including kiosk and single-app deployments.
Learn moreManaged Apple Accounts
The organisation-issued identity that Shared iPad sign-in depends on.
Learn moreZero-touch Apple deployment
Getting devices supervised and configured before anyone touches them, which Shared iPad requires.
Learn moreOfficial documentation
- Apple Platform Deployment, Apple Support
- Apple Business Manager User Guide, Apple Support
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 looks uncomfortable, the fix is device capacity, and it is far cheaper to decide that before the order goes in. We will run the full sizing with you; initial reply within 4 business hours.