# Studio

The **Studio** in Inistate is an administrative segment within the workspace, designed to enable users to configure and manage workflows and forms for their processes. It allows for customization of modules, design of forms, configuration of data flows, and creation of activities and states, all without the need for coding.

## Interface Overview

The Studio interface is divided into three main sections:

1. [**Workspace Menu Bar (Left Blue Panel)**](/home/workspace.md)
2. [**Module Management Area**](/home/module.md)
3. [**Design Area**](#design-area)

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

### Design Area

This panel provides tools for customizing selected modules and consists of several sections:

#### [**Basic**](/home/features/basic.md)

The Basic section is where users configure the general form design for different stages, such as *Create*, *Edit*, and *View*. Here, fields are specified for each stage of interaction:

These options provide a flexible range of functionalities for managing each form's lifecycle and accessibility.

#### [**Listing**](/home/features/listing.md)

The **Listing** section allows users to define custom lists based on specific criteria. These lists are used to display data in the form of lists that meet particular conditions.

Users can add new listings as needed, allowing for tailored views of module data based on their requirements.

#### [**Information**](/home/features/information.md)

The **Information** section is where users define the types of information that will be collected within the module. Different data types are supported, including:

Each information type has a customizable label and icon, and users can add new fields as needed to collect the required data in a structured format.

#### [**Template**](/home/advanced/template.md)

The **Template** section provides tools for document generation and import capabilities:

* **Print Form**: Allows users to create PDF templates for printing, using the data collected in the form.
* **Excel Import**: Enables data import via Excel sheets, using information from the module.

Templates are essential for creating structured outputs of the data within a module, especially for reporting purposes.

#### [**Activity**](/home/features/activity.md)

The **Activity** section is used to define the actions that users can perform within a module.

Activities often correspond to tasks or approvals in a workflow and are customizable based on the requirements of the module.

[**State**](/home/features/state.md)

The **State** section is used to define the different states that data can exist in.

A state is typically changed as a result of an activity (e.g., an *Approve* activity might move the data to an *Approved* state).

[**Flow**](/home/features/flow.md)

The **Flow** section is the mechanism that links **Activity** and **State** together, defining the transitions between states.

***

## Additional Features

The Studio interface also includes the following additional features:

**Save and Publish**

* Options located in the top-right corner allow users to save changes or publish the updated module configuration.

**Run Mode**

* A toggle switch between *Client* and *Builder* modes, allowing users to test configurations directly within the Studio.

[**Builder Mode**](/home/configuration/builder.md)

* An option to switch to the Builder section for making further changes in design and modify workflow applications for mobile and desktop views.


---

# 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/configuration/studio.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.