{"version":"2.1.273","anchor":"new-egress-permission-scope-constant-added","canonical_anchor":"new-egress-permission-scope-constant-added","heading":"New egress permission scope constant added","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-egress-permission-scope-constant-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### New egress permission scope constant added\n\nA new 'egress' entry was added to an internal permission scope list\n\n**Unclear.** What this `[\"required\", \"egress\"]` list is used for, and which feature or permission check it belongs to, is not shown by the evidence.\n\n**What**\n\nA new small list was added internally pairing the values `required` and `egress`. There's no surrounding context showing exactly where this list is used.\n\n**Why**\n\nThis looks like it relates to network egress (outbound connection) permission scoping, but what it controls or when it takes effect isn't shown.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}