> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/administrator-documentation/case-type-settings/core-case-data-visibility.md).
# Core Case Data Visibility
This lesson will show you how to edit the visibility of case core data.
## Access Core Case Data
Core case data is the information displayed above the case toolbar in every case. As the name suggests, it is the basic information concerning that case and does not change depending on case type. However, you may not want all of this information to be visible to users as a default, so it is possible to hide these fields.
To change the visibility of core case data, access the "Core Case Data" page by clicking the button on the settings menu under "Core Case Data".
## Edit Case Details Visibility
On the core case data page, you will be presented with a number of checkboxes, each corresponding to a field of core case data.
To toggle their visibility, check the box of the fields you want to see and uncheck the box of any fields you want to hide. In this example, we will remove the "Client Reference Number" and "Planned Completion Date" fields.
After you have finished, click "Save Changes" to enact the changes you have made.
## Before Editing
This is the core case data display before editing. As you can see, the "Client Reference Number" and "Planned Completion Date" fields are visible.
## After Editing
This is the same screen after editing. Now the fields that were unchecked have been hidden.
## Viewing Hidden Data
When case core data is hidden, a small arrow icon will appear in the bottom-right corner of the table. Clicking this will expose any hidden case data; clicking it a second time will hide the data once more.
---
# 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://docs.agilecase.com/administrator-documentation/case-type-settings/core-case-data-visibility.md?ask=&goal=
```
`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.