fix: field visibility on create-first-user screen#17008
Open
deepshekhardas wants to merge 1 commit into
Open
Conversation
deepshekhardas
requested review from
AlessioGr,
JarrodMFlesch and
jacobsfletch
as code owners
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.
Fields with \�ccess.read: false\ were still shown on the create-first-user screen because field permissions were granted
ead: true\ and \update: true\ for all fields unconditionally.
Fix: Set base field permissions to { create: true }\ only, so that per-field access controls are respected. The \docPermissionsForForm\ at the document level already grants \create: true,
ead: true, \update: true, so the document is fully accessible — only field-level read/update restrictions are preserved.