Kernel indexing permissions for special content

Indexing for Content Reuse

Kernels that are created from reused content will honor the Destination page permissions. This will affect the Lock / Unlock status of Source Articles used to create a generative response as follows:

Source page Privacy	Destination page Privacy	Lock / Unlock for Source page	Lock / Unlock for Destination page
Private	Public	Lock	Unlock
Semi-Private	Public	Lock	Unlock
Semi-Public	Public	Unlock	Unlock
Public	Public	Unlock	Unlock
Public	Private	Unlock	Lock
Public	Semi-Private	Unlock	Lock
Public	Semi-Public	Unlock	Unlock

Indexing for Conditional Content

Indexing Conditional Content respects the page privacy page. This means that the privacy of the conditional content block is ignored.

Source page Privacy	Conditional Content on page?	Lock / Unlock for Source page
Private	Yes	Lock
Private	No	Lock
Semi-Private	Yes	Lock
Semi-Private	No	Lock
Semi-Public	Yes	Unlock
Semi-Public	No	Unlock
Public	Yes	Unlock
Public	No	Unlock

Attachment indexing and the llm-no-index tag

The llm-no-index tag also applies to embedded media on your articles. This means that if the tag is applied to the source page, .doc/.docx and .pdf attachments will not be indexed. Other attachment types will not be indexed, regardless of whether or not the tag is applied to the page.

Attachment type	llm-no-index on Source page	Indexed?
.doc, .docx	Yes	No
.doc, .docx	No	Yes
.pdf	Yes	No
.pdf	No	Yes
Any other file type	Yes or No	No

Content Reuse indexing with the llm-no-index tag

The llm-no-index tag does not cascade to pages that contain Content Reuse. This means that only the page that has the llm-no-index tag will not be indexed, and you will have to apply the tag to destination pages.

llm-no-index on source page	llm-no index on destination page	Source indexed?	Destination indexed?
Yes	No	No	Yes
No	Yes	Yes	No
Yes	Yes	No	No
No	No	Yes	Yes