What it actually is
MIPACE Organisation runs alongside the personal MIPACE platform, using the same accounts, the same child profiles, the same public profile engine, and the same physical devices. It doesn’t create a second, separate system , it adds an organisation layer on top of the one that already exists, so a device an organisation provisions still resolves through exactly the same tap-to-profile mechanism as any personally bought device.
The structure
MIPACE Organisation is built around a clear hierarchy, so responsibility can be delegated without losing oversight:
Organisation → Account managers → Locations → Location managers → Groups → Group managers → People → Parent/guardian MIPACE account → Child MIPACE profile → Organisation-owned device
- An account manager manages the whole organisation.
- A location manager is restricted to the location(s) they’re mapped to.
- A group manager can view their assigned groups (for example, a class or a team).
- A person record links to a real parent or guardian’s own MIPACE account and the child profile they manage there.
The information never gets copied
This is the single most important thing to understand about how MIPACE Organisation works: it never duplicates a child’s medical or personal information into a second, organisation-held record. The organisation assigns a device to a person; the parent or guardian connects that device to their own child’s existing MIPACE profile. From that point on:
Parent updates their child’s profile → same MIPACE profile → same device resolves to it → next tap shows the current information.
The organisation manages devices and structure. The parent remains the source of truth for what’s actually on the profile.
Devices, provisioned and tracked centrally
Devices are provisioned directly into an organisation by MIPACE platform administration , in bulk, up to 5,000 at a time , and tracked through a live inventory showing what’s available, assigned, or retired. Location and account managers can then assign an available device to a person and, later, release it back to available stock if that person leaves or a device needs to move. Managers can’t create, delete, or retire device stock themselves , that stays under platform control, which keeps the organisation’s device inventory trustworthy and auditable.
The parent stays in control
When a location manager adds a person and enters a parent’s email, MIPACE sends a notification , not a special login of its own , telling the parent to sign in through their normal MIPACE account and review Your Devices, where the pending assignment appears. The parent reviews exactly which organisation, which device, and which of their children’s profiles is involved, and approves it themselves. The review and approval are completed through the recipient’s existing MIPACE account. Once approved, the device shows in their account as an organisation-owned device linked to me , visible, but not something they can rename, reassign, or deactivate themselves, since it belongs to the organisation’s inventory.
Full audit trail
Every organisation-level action , creating the organisation, adding or removing a manager, creating or deleting a location or group, provisioning or assigning or releasing a device, sending an invitation , is logged. Account managers can see their organisation’s own audit; platform administrators can see it across every organisation.
Where this fits
See how this plays out in specific settings: Schools & Nurseries · Care Providers · Clubs & Teams · Construction & Commercial Sites