Frequent elevation prompts produce unthinking consecutive approval

What it is

Privilege-prompt approval automation occurs when elevated requests appear consecutively within a task or routinely at high frequency, teaching approval as a fixed way to resume work instead of a separate check of requester, capability, and scope. It is a privilege-specific consequence of warning fatigue: every click grants actual authority.

Why it happens

An application splits work into operations needing similar authority while the system prompts for each. Users predict that approval is the only route forward. Fixed buttons, clustered requests, and a legitimate first prompt build action momentum in which a malicious request can hide. More prompts appear to add control but reduce the informational value of each decision.

Studying it

In a controlled installation or administration task, vary number, spacing, and requester and insert an unnecessary or differently scoped request late. Measure item-level comprehension, rejection of anomaly, latency, task completion, and effective authorization. Compare a trusted aggregate, task lease, and automatic background constraint. Never generate malicious prompts through real production administrator accounts.

Where it stops holding

Several confirmations can represent genuinely independent high-risk boundaries that should not be merged merely to reduce dialogs. First use, debugging, and specialist operations may involve dense decisions. The aim is to remove repetitive homogeneous requests while preserving anomalies, not bundle all power into one long-lived grant.

Applying it

• Combine necessary actions with the same requester, scope, and task into a short lease; confirm a scope change separately.
• Emphasize capability, target, and duration that differ from the previous request and prevent applications from timing prompts to create click momentum.
• Monitor elevation count per task, late-sequence latency, and anomaly rejection; repair architecture when the budget is exceeded.
• Rate-limit repeated requests and fail safely so prompt bombing cannot pressure approval.

Related

• Same group: O3.08.1 Explicit confirmation · O3.08.3 Elevation lifetime · O3.08.7 Batch requests
• Adjacent: O3.05.4 Warning habituation · O3.05.5 Faster click-through
• Search terms: privilege prompt fatigue · approval automation · authorization bombing