{"version":"2.1.268","anchor":"artifact-asset-readdelete-permission-check-refactored-to-a","canonical_anchor":"artifact-asset-readdelete-permission-check-refactored-to-a","heading":"Artifact asset read\/delete permission check refactored to a shared helper","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/artifact-asset-readdelete-permission-check-refactored-to-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Artifact asset read\/delete permission check refactored to a shared helper\n\nArtifact asset read\/delete permission checks now go through a shared internal helper\n\n**What**\n\nThe check that decides whether you're allowed to read or delete an artifact asset was rewired to use a shared internal helper function instead of a separate inline lookup, and this helper now throws its denial directly rather than returning a value to be checked.\n\n**Why**\n\nThis is an internal consistency change. It should not change what gets allowed or denied, but centralizes the logic so read and delete checks behave the same way.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}