{"version":"2.1.265","anchor":"writerclass-added-to-cowritten-artifact-metadata","canonical_anchor":"writerclass-added-to-cowritten-artifact-metadata","heading":"writerClass added to cowritten-artifact metadata","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/writerclass-added-to-cowritten-artifact-metadata","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### writerClass added to cowritten-artifact metadata\n\nCowritten artifact metadata now includes a writerClass derived from the user's permission role\n\n**What**\n\nMetadata attached to collaboratively-edited artifacts and documents, which already included `cowritten`, `agentDirect`, and `typeLocked`, now also carries a `writerClass` field. It is derived from whether the caller has an `owner` or `writer` permission role, and is used to decide whether a write applies to a single page or to the whole document.\n\n**Why**\n\nThis lets the system scope collaborative edits differently depending on the editor's role, so an owner and a writer may not always have the same write scope on a shared artifact.\n\n- Area: Artifacts\n- Names: `writerClass`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}