> For the complete documentation index, see [llms.txt](https://docs.rhinofcp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhinofcp.com/data-schemas/data-schema-field-attributes-and-field-permissions.md).

# Data Schema Field Attributes and Field Permissions

Provides information on data schema field attributes and field permissions

## Data Schema Field Attributes

![](https://content.gitbook.com/content/ydySyCBmy6F7NnGn4bPa/blobs/uF4HEPLDhnjMN6OYk15i/27765396062237)

For each field in the Data Schema, the following attributes are defined:

* **Name:** the name of this field
* **Identifier:** the string by which this field should be identified in the input data (if empty, the Name field will be used for identification)
* **Description:** a description of the field (including any information that can help collaborators put the data in the correct format)
* **Type:** the name of the field type. Please refer to [Supported Data Schema Data Types](/data-schemas/supported-data-schema-data-types.md) for a full list of supported data types within the Rhino FCP
* **Type Params:** any parameters for the field type (e.g., min/max values for a ContrainedInt type). Please refer to [Supported Data Schema Data Types](/data-schemas/supported-data-schema-data-types.md) for a full list of supported parameters for each data type within the Rhino FCP
* **Units:** the units in which the values of this field are expected to be. These units will also appear in charts showing aggregate values from this field in the Rhino UI
* **Sensitive Data:** whether or not this field may contain sensitive data
* **Aggregate Statistics:** the field's underlying data is only persisted on-prem, and **NO** aggregate statistics can be viewed in the cloud. This field can be viewed via Secure Access, given the proper permissions.
* **Secure Access:** the field's underlying data is only persisted on-prem, and aggregate statistics can be viewed in the cloud. **This field isn’t viewable via Secure Access.**

## Data Schema Field Permissions

For each variable defined within a schema, one of the following permission profiles can be applied:

* **Default:** The variable's underlying data only persists on-prem, and aggregate statistics can be viewed in the cloud. This field can be viewed via secure access given the proper permissions.
* **No Aggregate Statistics:** The variable's underlying data only persists on-prem, and **no aggregate statistics** can be viewed in the cloud. This field can be viewed via secure access given the proper permissions.
* **No Secure Access:** The variable's underlying data only persists on-prem, and aggregate statistics can be viewed in the cloud. **This field isn’t viewable via secure access.**
* **Local Only:** The variable's underlying data only persists on-prem, and **no aggregate statistics** can be viewed in the cloud. **This field isn’t viewable via secure access.**


---

# 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.rhinofcp.com/data-schemas/data-schema-field-attributes-and-field-permissions.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.