docs(permissions): Attachments Access page + ADR-0057 sys_upload_session guard note#3009
Merged
Merged
Conversation
…ion guard note Documents the attachment access model landed across #2984/#2999/#2538 (#2970): parent-derived read/create/delete, inherited list visibility, authenticated parent-scoped downloads, the enable.files opt-in gate, the member_default no-delete-baseline caveat, the storage-byte lifecycle (sys_file + sys_upload_session reap guards), and an enforcement-summary + error-code table. Registered in permissions/meta.json. Also names sys_upload_session as the second reap-guard consumer in the ADR-0057 amendment. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0187NT3Qer9oep5dCRb9b8Lt
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation for the attachment access/security model landed across #2984 + #2999 (framework) and #2538 (objectui), tracked in the now-closed #2970. No code changes.
New page —
content/docs/permissions/attachments-access.mdxA single authoritative summary of how access to record attachments is decided:
sys_attachment(join) +sys_file(blob) inherit the parent record's access (Salesforce ContentDocumentLink parity);Field.file/Field.imageare a separate path.enable.filesopt-in gate (FILES_DISABLED).ATTACHMENT_PARENT_ACCESS);uploaded_byserver-stamped.sys_attachment-scoped middleware (sototalcan't leak the hidden count).ATTACHMENT_DELETE_DENIED), with themember_defaultno-delete-baseline caveat (management needs a granted set).AUTH_REQUIRED/ATTACHMENT_DOWNLOAD_DENIED); non-attachments files (avatars, field images) keep their<img>-embeddable capability URL.sys_file+sys_upload_sessionreap guards.enable.files, the storage-service contract, Authorization Architecture, and ADR-0049/0057/0066.Registered in
permissions/meta.json(after Field-Level Security).ADR-0057
Names
sys_upload_sessionas the second reap-guard consumer in the reap-guards amendment (alongsidesys_file).Verification
check:doc-authoring✓ (195 files clean)./adr/route prefix (matching existing pages),meta.jsonis valid JSON,<Callout>is a component already used in this section.content/docschanges).🤖 Generated with Claude Code
Generated by Claude Code