> For the complete documentation index, see [llms.txt](https://inistate.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inistate.gitbook.io/home/configuration.md).

# Configuration

Inistate provides a comprehensive set of configuration tools for designing, managing, and previewing workflow applications. It consists of two main sections: [**Studio**](/home/configuration/studio.md) and [**Builder**](/home/configuration/builder.md), each offering unique functionality for configuring modules, designing workflows, and previewing application layouts.

### Workspace Navigation and Menu

Both **Studio** and **Builder** include a **Workspace Menu Bar** on the left side, providing access to key workspace functions, such as user controls, notifications, and a list of available modules (for studio - builder module list is on the right). This menu ensures easy navigation between different parts of the configuration interface and the workspace itself.

### Module Management

A **Module Management Area** appears in both sections, providing tools to customize modules by configuring listings, data fields, templates, workflows, and activities. In both **Studio** and **Builder**, users can add, modify, and manage these aspects without needing code. This consistency in module setup allows users to maintain data integrity and workflow logic across the application.

### Form Design and Listing Configuration

Each section allows users to define how forms are displayed, organized, and filtered:

**Form Design**

* Users configure the Create, Edit, and View stages for each form.

**Listing Configuration**

* Users can create custom lists based on specific criteria for data display.

**Information Fields**

* Users specify the types of data (e.g., text, number) collected in each module.

### Workflow and State Management

In both **Studio** and **Builder**, users can define workflows that control how data moves through the application. This includes setting up:

#### **Activities**

* Actions users can perform within a module (e.g., approving a request).

#### **States**

* Different statuses that data can transition through within the workflow.

#### **Flow**

* Defines transitions between states, linking activities to specific outcomes.

### Preview and Testing

Both sections allow for testing configurations in real-time:

#### **Preview Options**

* Users can switch between mobile and desktop views, reload previews, and go Fullscreen.

#### **Run Mode**

* A "Run" button at the top allows users to test their application directly within the configuration environment.

### Unique Features in Studio and Builder

While **Studio** focuses more on the backend configuration and setup of modules, **Builder** provides a live preview of the app’s interface, simulating how it will appear on both mobile and desktop devices. **Builder** also includes a **Bottom Navigation Bar** in the mobile preview, allowing users to test navigation and app flow from an end-user perspective.