{"version":"2.1.257","anchor":"separate-consent-slugs-for-artifact-handlers-readwrite","canonical_anchor":"separate-consent-slugs-for-artifact-handlers-readwrite","heading":"Separate consent slugs for artifact handlers read\/write","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/separate-consent-slugs-for-artifact-handlers-readwrite","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Separate consent slugs for artifact handlers read\/write\n\nArtifact handler scripts get their own read and write consent tracking, separate from artifact assets.\n\nFour new consent-tracking fields \u2014 `artifactHandlersReadConsentSlugs`, `artifactHandlersReadHumanConsentSlugs`, `artifactHandlersWriteConsentSlugs`, and `artifactHandlersWriteHumanConsentSlugs` \u2014 were added alongside the existing artifact asset consent slugs. Artifact \"handlers\" (scripts) now get their own read\/write consent gate distinct from artifact assets.\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}