{"version":"2.1.251","anchor":"network-access-permission-asks-can-say-which-background-work","canonical_anchor":"network-access-permission-asks-can-say-which-background-work","heading":"Network-access permission asks can say which background worker raised them","tier":"internal","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/network-access-permission-asks-can-say-which-background-work","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Network-access permission asks can say which background worker raised them\n\nNetwork permission asks can now name the background worker that raised them.\n\n**What**\n\nA request to allow sandboxed network access now carries two optional fields naming the background worker it came from, so the permission prompt and telemetry can tell a worker-originated ask apart from one made by the main session.\n\n**Details**\n\n- The fields are a forwarded-from-worker flag and the worker's name; a caller sets both, and a consumer reads the flag into the request's source.\n- No flag guards it: callers exist on both the sending and receiving side.\n\n**Evidence**\n\n`forwardedFromWorker: N(!0).optional()`\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}