{"version":"2.1.265","anchor":"artifact-database-writes-gain-as-level-and-version-pinning","canonical_anchor":"artifact-database-writes-gain-as-level-and-version-pinning","heading":"Artifact-database writes gain as_level and version pinning","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/artifact-database-writes-gain-as-level-and-version-pinning","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Artifact-database writes gain as_level and version pinning\n\nArtifact database reads\/writes can now use a reduced access level and pin to a document version\n\n**What**\n\nArtifact database `write_db` and `read_db` calls can now pass an `as_level` parameter set to `interact` or `admin`, letting Claude act with a reduced access level to test what a less-privileged viewer would be able to do. Writes can also pin themselves to a specific document version using `if_version`, which fails with a `version_mismatch` error if the document was changed in the meantime.\n\n**Why**\n\n`as_level` lets you check how an artifact behaves for users with limited permissions, and `if_version` protects against accidentally overwriting a document that changed since it was last read.\n\n- Area: Artifacts\n- Names: `as_level`, `if_version`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}