{"version":"2.1.239","anchor":"artifact-actions-reject-approval-fields-that-no-permission-c","canonical_anchor":"artifact-actions-reject-approval-fields-that-no-permission-c","heading":"Artifact actions reject approval fields that no permission check issued","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/artifact-actions-reject-approval-fields-that-no-permission-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Artifact actions reject approval fields that no permission check issued\n\nArtifact actions carrying approval fields nobody issued are denied outright.\n\n**What**\n\nIf an artifact action arrives with internal approval fields that no completed permission check attached to that call, the action is denied and the permission classifier cannot approve it. The denial message points at hooks or SDK hosts injecting the fields. This check always runs.\n\n**Evidence**\n\n`Artifact consent markers not minted by a completed permission check fail closed`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}