From 1a3310b87d7b0f84268c2b80b53b93744b780699 Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Thu, 3 Sep 2026 01:51:15 +0000 Subject: [PATCH] Document private field searchability default behavior Add documentation explaining that newly created private fields default to non-searchable (searchable: false) to prevent private content from appearing in _q search results. Existing private fields retain their current searchability settings. Relates to https://github.com/strapi/strapi/pull/27482 --- docusaurus/docs/cms/features/content-type-builder.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docusaurus/docs/cms/features/content-type-builder.md b/docusaurus/docs/cms/features/content-type-builder.md index 937baee987..b41350c349 100644 --- a/docusaurus/docs/cms/features/content-type-builder.md +++ b/docusaurus/docs/cms/features/content-type-builder.md @@ -212,6 +212,10 @@ In the 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. +::: +