{"version":"2.1.286","anchor":"unattended-permission-mode-own-record-stopped-sentinel-wi","canonical_anchor":"unattended-permission-mode-own-record-stopped-sentinel-wi","heading":"A new own_record option for unattended permission handling","tier":"use","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/unattended-permission-mode-own-record-stopped-sentinel-wi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### A new own_record option for unattended permission handling\n\nA permission setting now accepts `own_record` for unattended sessions, and one more outcome now counts as stopped\n\n**Unclear.** Which configuration this belongs to and what `own_record` does are not known.\n\n**What**\n\nA permission configuration can now set its unattended behaviour to `own_record`. Unattended sessions are ones running without a person present to answer permission prompts. Separately, one more internal outcome is now reported as stopped.\n\n**Why**\n\nThis affects how sessions that run with nobody watching deal with permissions.\n\n- Area: Permissions\n- Names: `own_record`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 4\/5"}