Skip to content

docs(permissions): attachments-access states the stored form of a file field as the sys_file id #17695

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-bill merged 1 commit into from
Sep 11, 2026
+5 −3
Merged

docs(permissions): attachments-access states the stored form of a file field as the sys_file id #17695

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions content/docs/permissions/attachments-access.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,9 +17,11 @@ inherits its parent record's.** A caller who can read a record can read its
attachments; a caller who can edit a record can attach to and detach from it.
Enforcement is layered, and every gate is fail-closed.

`Field.file` / `Field.image` are a **separate** path — those store a file URL
in the record's own column and never create a `sys_attachment` row, so nothing
on this page applies to them.
`Field.file` / `Field.image` are a **separate** path — those store an opaque
`sys_file` id in the record's own column (ADR-0104 D3; the
`{ id, name, size, mimeType, url }` shape is derived at read time, never
stored) and never create a `sys_attachment` row, so nothing on this page
applies to them.

## The opt-in gate — `enable.files`

Expand Down
Loading