Docs: Document the _access REST-only enforcement boundary (refs #109)#114
Merged
Conversation
github-project-automation
Bot
moved this from New
to Merged
in adapt-authoring: The TODO Board
github-actions Bot
pushed a commit
that referenced
this pull request
Jul 14, 2026
## [4.1.1](v4.1.0...v4.1.1) (2026-07-14) ### Chore * replace legacy new.yml with direct add-to-project workflow ([a061f6d](a061f6d)) ### Docs * Document the _access REST-only enforcement boundary (refs #109) (#114) ([f853ea9](f853ea9)), closes [#109](#109) [#114](#114) ### Fix * Check write access against the target document (fixes #115) (#116) ([9c4c139](9c4c139)), closes [#115](#115) [#116](#116)
|
🎉 This PR is included in version 4.1.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
1 participant
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.
Refs #109
Docs
_accessenforcement boundary inwriting-an-api.md, alongside the access-hook docs:_accessis enforced only on the REST request layer (accessCheckHook/accessQueryHookare request-scoped). Preview/publish/export and server-side/programmaticfind()bypass it by design (noreq.authoutside a REST request; internal paths use coarse build scopes)._accessis sharing, not a security boundary) and when to revisit (multi-tenant isolation → thread an identity context into the code API).Notes
refs #109(notfixes): Access enforcement boundary: _access is REST-only by design — track bypass paths #109 is a tracking record for the deliberate design boundary and should stay open.