{"version":"2.1.260","anchor":"egress-allowlist-entries-now-carry-human-readable-purposes","canonical_anchor":"egress-allowlist-entries-now-carry-human-readable-purposes","heading":"Egress allowlist entries now carry human-readable purposes","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/egress-allowlist-entries-now-carry-human-readable-purposes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Egress allowlist entries now carry human-readable purposes\n\nEgress allowlist entries now explain in plain language why each host is contacted.\n\nEvery entry in `EGRESS_SERVICES`, the desktop app's network egress declaration used for firewall\/allowlist UI, now includes a human-readable `purpose` message explaining why that host is contacted, plus a `firewallAlsoPurpose` field for secondary hosts. These are surfaced to admins and users deciding what network access to allow.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}