Confirmation must explain what capability will be gained

What it is

Consequence-centered privilege explanation translates labels such as administrator, accessibility, or full-disk access into the actions, objects, and boundaries the requester gains. The decision is not whether a permission name is familiar, but which data the application can read, what it can control, how long authority lasts, and whether it can act as the user.

Why it happens

Platform names follow implementation categories while user goals follow tasks, creating a semantic gap. “Advanced permission required” drives approval from brand trust or task pressure; a long API list instead hides consequential power. Organizing around high-impact capability and task necessity lets users compare requested authority with expected function.

Studying it

Before showing a technical permission name, ask participants which capabilities a task should require. Then compare explanations and test restatement of readable objects, executable actions, duration, and refusal consequence. Reconcile comprehension with runtime permission inventory and behavioral probes. Terminology recall and approval rate do not establish understanding of the actual boundary.

Where it stops holding

The explanation cannot promise that every capability will be exercised or enumerate all future abuse. Security-sensitive internals may stay hidden, but user-relevant power cannot disappear with them. Managed-device policy may authorize on a person's behalf and should still communicate capability and responsibility boundaries to affected users.

Applying it

• Answer “who can do what to which object, until when” at the first layer and place technical permission names beneath it.
• Emphasize deletion, recording, sending as the user, and reading other applications' data, explaining necessity for the current feature.
• Generate disclosure from the effective authorization set and probe behavior; block release for any undisclosed capability.
• State which feature genuinely stops after refusal instead of claiming the whole application is unusable.

Related

• Same group: O3.08.1 Explicit elevation · O3.08.6 Ambiguous wording · O3.08.5 Scope expansion
• Adjacent: O2.02 Permission explanation · O3.06.3 Sensitive-action confirmation
• Search terms: privilege capability disclosure · permission consequence · authorization comprehension