> 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/getting-started/disabling-case-level-functions-and-core-case-data.md).

# Disabling Case Level Functions and Core Case Data

<figure><img src="/files/ShQdjjQ1Taf2s6Ci20SP" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/ZQJ9luZCtCA7SxFxNc3n" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/B9wBN8l1fOybBNAJo1SA" alt=""><figcaption></figcaption></figure>

In the final part of our getting started guide, we will show you how to edit the visibility of case level functions and case core data in your system.

The default layout of AgileCase allows a wide range of information to be entered. However, depending upon your industry and the particulars of your business, it may or may not be appropriate to disclose some of this information. The ability to edit case level functions and core case data allows you to hide this information or any unnecessary data on your system.

{% stepper %}
{% step %}

## Edit case level functions

Case level functions are edited through **Tab Visibility**. Tab visibility controls what tabs are visible on the case screen, governing the information that users have access to.

You can edit this by selecting **“Tab Visibility”** from the settings menu.

You can then set the tabs you do not want to be visible as **“Disabled”**.

In this case, we will remove the **“Transactions”** tab from the **“General Work”** case type. You can add different tab visibility configurations for each of your case types.
{% endstep %}

{% step %}

## Edit core case data

Core case data governs the core fields that are available in each case.

To edit this, select **“Core Case Data”** from the settings menu.

You can then simply check or uncheck the core fields that you wish to be available in each case.

While core case data consists of the basic information concerning each case, some details such as financial information may not be appropriate to disclose. Other fields may simply be unnecessary for your business practices.

In this example case, we will remove the **"Case Description"** field.
{% endstep %}
{% endstepper %}

With these two options, you can edit the information that is available to system users, allowing you to protect sensitive data or remove unnecessary functions.

With your case level functions and data edited to your preference, you have finished setting up your AgileCase account. You are now in a position to begin using AgileCase to manage your business and explore the deeper functionality we provide.


---

# 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/getting-started/disabling-case-level-functions-and-core-case-data.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.
