{"version":"2.1.260","anchor":"sandbox-read-deny-settings-now-called-out-alongside-read-rul","canonical_anchor":"sandbox-read-deny-settings-now-called-out-alongside-read-rul","heading":"Sandbox read-deny settings now called out alongside Read rules in withheld-file explanations","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/sandbox-read-deny-settings-now-called-out-alongside-read-rul","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Sandbox read-deny settings now called out alongside Read rules in withheld-file explanations\n\nFile-withheld explanations now also mention sandbox read-deny settings as a cause.\n\nMessages explaining why files were withheld from git or context now mention a sandbox read-deny setting as a possible cause, in addition to a Read permission rule. This appears both in the credential-scrub explanation and the git-upload refusal message, and similarly in messages about files left out of a cloud\/session upload.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}