# State

<figure><img src="/files/TycdJ5a0y9WkBHr5xelM" alt=""><figcaption><p>The area within the red frame highlights the State panel.</p></figcaption></figure>

## **Assigning States**

States are typically assigned at the start of an entity's lifecycle and updated based on actions performed. The State's color will automatically be assigned by the system, but the users can apply different colors to States to classify them easily.

<figure><img src="/files/Qbyg7pcvduWNC26LT6xf" alt="" width="563"><figcaption><p>Assign color to State</p></figcaption></figure>

## Advanced Settings

### Initial

The function serves as the starting point for any application, encapsulating the basic settings and configurations that define how the application will function before any modifications or enhancements are made by the user.

### Celebrate \[Beta]

This feature allows users to enhance their interaction experience by enabling a festive confetti effect. When this function is toggled on, the confetti visual effect is triggered upon the successful submission of the form. It is designed to create a celebratory atmosphere, thus improving user satisfaction and engagement.

### Disable User \[Beta]

It allows user to deactivate another user's account by change the state. Once disabled, the user will no longer have access to the system's features, data, or functionalities until the account is reactivated. This function is useful for managing user permissions and ensuring security compliance.

***

## Best Practices

* **Clarity**: Ensure each State name clearly reflects its purpose.
* **Consistency**: Apply similar State names across different modules to maintain uniformity.
* **Simplicity**: Avoid overly complex or unnecessary States that don’t add value.


---

# Agent Instructions: 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://inistate.gitbook.io/home/features/state.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.
