{"version":"2.1.248","anchor":"managed-settings-consent-can-no-longer-be-answered-by-an-in-","canonical_anchor":"managed-settings-consent-can-no-longer-be-answered-by-an-in-","heading":"Managed-settings consent can no longer be answered by an in-flight keypress","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/managed-settings-consent-can-no-longer-be-answered-by-an-in-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Managed-settings consent can no longer be answered by an in-flight keypress\n\nA keystroke already in flight can no longer accept your organization's managed settings prompt.\n\n**What**\n\nThe managed-settings security prompt records when it rendered and ignores accept or reject until that window has passed, so a keystroke already on its way cannot approve your organization's settings.\n\n**Details**\n\n- Renders with an explicit reveal mode of `default` when not arriving from a login handoff.\n\n**Evidence**\n\n`Managed-settings consent dialog exited without an answer`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}