> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/product-news/2026/readme/allow-ability-to-hide-arbitrary-field-or-section-from-sharing-view.md).

# Allow ability to hide arbitrary field or section from sharing view

## Problem

When an assessment is shared with other assessors or verifiers, all fields and sections are visible. Some organisations need to hide certain fields from the shared view -- for example, internal notes, administrative flags, or intermediate scoring calculations that are not appropriate for external parties to see.

## How it works

Assessment template authors can now toggle the visibility of individual fields and sections in the shared assessment view. Both fields and sections default to visible, so existing templates are unaffected.

### Configuration

In the assessment form builder, a "Shared Assessment" checkbox appears under the **Review Workflows** section of the context bar for both fields and sections. Unchecking it hides that field or section when the assessment is shared.

A field is only visible in the shared view if **both** the field and its parent section have the checkbox enabled. Hiding a section hides all of its fields regardless of their individual settings.

The checkbox is only shown for assessment templates -- it does not appear on application form templates.

### What changes in the shared view

When a shared assessment is viewed, any fields or sections marked as hidden are excluded from the rendered output. The data is filtered server-side, so hidden content is not sent to the client at all.

This works alongside the existing "share scoring info" setting. When scoring info is shared, only fields marked as visible in the shared assessment view are included.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.tahua.io/product-news/2026/readme/allow-ability-to-hide-arbitrary-field-or-section-from-sharing-view.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.