Skip to content

Document private field searchability default behavior #3440

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

Draft
pwizla wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Document private field searchability default behavior #3440

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
4 changes: 4 additions & 0 deletions docusaurus/docs/cms/features/content-type-builder.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -212,6 +212,10 @@ In the <Icon name="layout" /> Content-type Builder, fields can be added at the c
Depending on what content-type or component is being created or edited, not all fields -including components and dynamic zones- are always available.
:::

:::info Private fields and search
When you mark a field as **Private field**, newly created private fields are automatically set to be non-searchable (searchable: false). This prevents private content from appearing in query results when using the `_q` search parameter. Existing private fields retain their current searchability settings unless you explicitly change them. If you need a private field to be searchable, you can enable it in the field's advanced settings.
:::

<ThemedImage
alt="Fields selection"
sources={{
Expand Down
Loading