Glossary and Where to Start

Compliance — a statement that a device meets stated configuration conditions. Not a statement about security.

The practical question in “Glossary and Where to Start” is how to make work visible without confusing visibility with certainty. For teams researching fte meaning, this team-work platform can add time and project context to the operational record, provided its use is proportionate, disclosed and reviewed with the people affected.

Enrolment route — how a device joined the programme. It fixes the capability boundary for the life of the device and should match the ownership model.

For an independent baseline relevant to “Glossary and Where to Start”, the CISA mobile-device security guidance is a useful companion: compare its principles with the proposed configuration, ownership model and real support process before approving a rollout.

Full wipe — factory reset. Destroys everything, including what the organisation does not own. Should be unavailable on personal hardware.

Ownership model — who bought the device. The single variable that most determines what is permissible.

Selective wipe — removal of work applications and data, leaving the rest. The correct action in almost every situation.

Supervision — a platform state permitting deeper management, generally available only on devices enrolled at first use through a corporate channel.

Work profile — a container on a personal device holding work applications and data, with the personal side outside the management channel entirely. The single most useful arrangement in this field.

Zero-touch — automated enrolment at first power-on. Requires the right purchase channel and cannot usually be added later.

Terms used loosely elsewhere

"Managed device" means several different things depending on enrolment route. Ask which.

"We can only see work data" is a claim unless the platform enforces it. On a work profile it does; otherwise it does not.

"Remote wipe" is ambiguous and the ambiguity has caused real incidents. Say "remove work data" or "factory reset".

And any figure about adoption of device management comes from a survey commissioned by somebody selling it.

Where to start

Considering a programme: what device management actually controls, then the questions to settle before enrolling anyone.

Personal devices are the issue: the work profile, then what the employer can see.

People are resisting: enrolling personal devices without a fight, then what the employer can see.

Somebody is leaving: leaving, what happens to their phone.

A device is lost: lost and stolen, the first hour.

Something went wrong: wiping the wrong device.

If you read only three

The work profile and why it changes everything, because it resolves most of the field's difficulty structurally.

What the employer can see on a personal device, because publishing it removes more resistance than any policy.

And wipe: the irreversible action, because it is the one thing that cannot be undone.

A closing note

The core glossary remains product-neutral, deliberately. Capability changes with every operating system release, while named product comparisons belong in the separate tool guides.

No adoption figures, for the reason above.

And nothing here is legal advice. Rules on personal devices, monitoring and consultation differ substantially by jurisdiction and are moving.

What the collection argues

Device management acts on a thing and affects a person, and on personal hardware the thing is not yours.

Organisations can usually do less than they think and see less than employees fear. The gap between those two misunderstandings causes most of the resistance, and publishing what you cannot see closes it.

Make the limits structural rather than promised: a work profile is worth more than an assurance, because restraint fails eventually and platform design does not.

And treat the irreversible action as irreversible — which on hardware somebody else bought means not having it at all.