> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/concepts/objects/custom-fields/special-field-types.md).

# Special Field Types

{% hint style="success" %}
**Audience:** Admins, Developers, Solution Architects

**Purpose:** Explains how special field types support advanced data modeling and helps administrators, solution architects, and developers select the appropriate field when designing <code class="expression">space.vars.object</code> schemas.
{% endhint %}

## Overview

Special field types are advanced fields that extend schema capabilities beyond simple data capture. These fields enable more sophisticated data modeling by supporting structured relationships, centralized file storage, and team-based ownership and responsibility.

Unlike basic field types, which store discrete values such as text or numbers, special fields influence how <code class="expression">space.vars.entities</code> connect to one another, how users collaborate, and how data is governed across the platform. Because of their broader impact, selecting and configuring these fields is an important architectural decision when designing scalable <code class="expression">space.vars.object</code> schemas.

Special field types are commonly used to:

* Model relationships between <code class="expression">space.vars.entities</code>
* Centralize supporting documents and assets
* Assign ownership or responsibility
* Enable collaboration and workflow routing

Understanding how these fields behave, and when to use them, helps prevent schema design issues that can affect reporting accuracy, <code class="expression">space.vars.automation</code> reliability, permissions, and long-term maintainability.

### Checkbox

The Checkbox field supports a single binary selection and is best suited for true/false style data points. This field stores a boolean-style value and is useful for capturing simple conditions or flags that influence filtering, automation, or <code class="expression">space.vars.entity</code> state.

#### Common Use Cases

Use a Checkbox field when capturing:

* Feature enabled or disabled states
* Confirmation indicators
* Simple eligibility flags
* One-time acknowledgements

#### Design Guidance

Choose a single Checkbox when only one binary condition is required. Avoid using this field when multiple selections or categorical values are needed, as selection-based field types are more appropriate in those cases.

{% hint style="info" %}
**Note:** If you need to have multiple selections or categorical values, use the multi-selection checkboxes field type.
{% endhint %}

### Files

The Files field allows <code class="expression">space.vars.entities</code> to store and reference uploaded documents or digital assets directly within the <code class="expression">space.vars.entity</code> context. Each uploaded file is stored as a separate asset, even if the same file is uploaded to multiple <code class="expression">space.vars.entities</code>.

#### Common Use Cases

Use a Files field to attach:

* Contracts or agreements
* Images or media assets
* Supporting documentation
* Operational resources
* Reference files

Centralizing files within <code class="expression">space.vars.entities</code> improves context, reduces dependency on external storage systems, and supports collaboration across teams. Uploaded files are automatically scanned for potential threats and may be removed if a virus is detected or suspected.

#### Behavior and Governance Considerations

Files are associated with the specific <code class="expression">space.vars.entity</code> where they are uploaded. Removing a file reference does not automatically remove the file from other <code class="expression">space.vars.entities</code> where it may exist.

Permissions determine whether users can upload, remove, or permanently delete files. Because files may contain sensitive information, access controls should be planned carefully. Thoughtful file organization helps prevent unnecessary duplication and keeps <code class="expression">space.vars.entities</code> manageable.

### Relationship

The Relationship field connects <code class="expression">space.vars.entities</code> across <code class="expression">space.vars.objects</code>, enabling structured associations within the data model. Relationship fields are foundational to modeling how entities relate to one another and play a critical role in schema architecture.

For more information, see [Object Relationships](/docs/concepts/objects/object-configuration/object-relationships.md).

#### Common Use Cases

Use Relationship fields to:

* Link contacts to organizations
* Associate deals with accounts
* Connect related operational <code class="expression">space.vars.entities</code>
* Model hierarchical or peer relationships

#### Behavior and Architecture Considerations

Relationship fields automatically create an inverse relationship on the related <code class="expression">space.vars.object</code>, enabling navigation in both directions.

Relationships support:

* Cross-<code class="expression">space.vars.object</code> reporting
* <code class="expression">space.vars.automation</code> triggers and conditions
* <code class="expression">space.vars.entity</code> navigation and context

When relationship fields contain many values, the platform summarizes them in timelines and API responses to maintain usability and performance. Because relationships define how data is interconnected, they should be designed intentionally to preserve data integrity, avoid ambiguity, and support long-term scalability. It is important to treat relationship fields as architectural components and not simple attributes.

### Team Selector

The Team Selector field assigns ownership or responsibility to specific team members within the organization. This field references active users and is commonly used to model accountability and collaboration.

#### Common Use Cases

Use a Team Selector field to:

* Assign <code class="expression">space.vars.entity</code> ownership in the system Owner field
* Route work to specific users
* Define responsibility for follow-up
* Support collaboration workflows
* Influence visibility and access

#### Permissions and Workflow Impact

Team-based assignments can affect permissions, workflow routing, and operational visibility depending on how access controls and <code class="expression">space.vars.automations</code> are configured. Align team assignments with organizational structure to ensure consistent governance and reduce confusion around responsibility and access.

***

## Additional Information

<details>

<summary>Schema Design Best Practices</summary>

When working with special field types:

* Use relationships instead of large selection lists when modeling connected data.
* Plan file access and permissions carefully to avoid governance issues.
* Align team assignments with workflow and access requirements.
* Treat relationship fields as architectural components, not simple attributes.

Intentional use of special fields strengthens data integrity, improves collaboration, and supports scalable system design.

</details>

***

## What’s Next

Review field-specific documentation before implementing schema changes to ensure the selected field type supports your operational, reporting, and integration requirements. Continue designing your schema with the following resources:

<details>

<summary>Related Topics</summary>

* [Date Field Types](/docs/concepts/objects/custom-fields/date-field-types.md)
* [Selection Field Types](/docs/concepts/objects/custom-fields/selection-field-types.md)
* [Numerical Field Types ](/docs/concepts/objects/custom-fields/numerical-field-types.md)
* [Text Field Types](/docs/concepts/objects/custom-fields/text-field-types.md)
* [Communication Field Types](/docs/concepts/objects/custom-fields/communication-field-types.md)

</details>


---

# 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:

```
GET https://developer.kizen.com/docs/concepts/objects/custom-fields/special-field-types.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.