{"version":"2.1.228","anchor":"artifact-database-data-users-me-resolves-to-your-own-user-id","canonical_anchor":"artifact-database-data-users-me-resolves-to-your-own-user-id","heading":"Artifact database data\/users\/me resolves to your own user id","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/artifact-database-data-users-me-resolves-to-your-own-user-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Artifact database `data\/users\/me` resolves to your own user id\n\nArtifacts can address your own user record as \"me\" instead of looking up your id.\n\n**What**\n\nAn artifact reading or writing the `data\/users` collection can use the document id `me` and it is rewritten to the caller's real user id. The id is fetched once and cached per account, with concurrent lookups sharing one request.\n\n**Details**\n\n- If the artifact's published version does not declare both the database and user capabilities, the error says the artifact needs republishing rather than failing opaquely.\n\n**Evidence**\n\n`resolving 'me' needs this artifact's published version to declare the db and user capabilities`\n\n- Area: Artifacts\n- Names: `data\/users\/me`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 3\/5"}