{"version":"2.1.275","anchor":"artifact-copy-access-checks-now-special-case-type-locked-a","canonical_anchor":"artifact-copy-access-checks-now-special-case-type-locked-a","heading":"Artifact 'copy' access checks now special-case type-locked artifacts","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/artifact-copy-access-checks-now-special-case-type-locked-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Artifact 'copy' access checks now special-case type-locked artifacts\n\nCopying a type-locked artifact now goes through a dedicated access check instead of the generic one\n\n**Unclear.** The finding doesn't say what the dedicated check does differently from the generic one, or what a type-locked artifact is.\n\n**What**\n\nThe function that checks whether a user can access an artifact now takes a `mode` parameter, defaulting to \"copy\". When that mode is used on an artifact that is locked to a specific type, the check is now routed through a dedicated function instead of the general ownership\/read check that other access requests use.\n\n**Why**\n\nThis lets copy permission for type-locked artifacts be evaluated with its own dedicated logic, separate from ordinary read access.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}