🏗️ Studio

🎯 Overview

This interface brings together all the elements necessary for creating, configuring and deploying your Apps.

You can configure your Apps through several tabs in the side editor, and navigate between your Apps through the tabs at the top of the page. In the central space of the page, you will find the Blocks and their content.

The sidebar is composed of six tabs, each allowing you to adjust different elements of your App:

📱 App

The homepage of your App

🌳 Hierarchy

The tree structure of your blocks

🧙‍♂️ Wizard

The assistant and its workflow

🏷️ Attributes

Debug mode and attribute testing

🔗 API

API management and tokens

⚙️ Settings

For AI parameters

📱 App Tab

This is where you can define how your App presents itself and which Users have the right to access it.

🏷️ Logo and App Name

Click on the App title to modify it directly, and do the same for the logo.

Supported image formats for the logo are JPEG or PNG.

📝 Description

To briefly present your App.

🔐 Restrict Access To

You can choose whether this App should be accessible by all Users of your Team or only to certain User groups. The change is immediate, you don't need to publish a new version of the App when modifying access rights.

For more information on roles and Groups, consult this documentation : 👥 Team Management

🚀 Publish Current Version

Administrators and Architects of the Team constantly see Apps in a "preview" version, which allows them to work without impacting Apps in production. In preview, changes made to blocks and the wizard are visible in real-time, with each adjustment being effective immediately.

Users see Apps that are:

Accessible to them through their Group(s) or those available to the entire Team (according to the "Restrict access to" field configuration of Apps)

Already published at least once (a v1 or higher must exist)

In their latest version. Previous versions of the App will only work to access an old publication from their publication history

📘 Important: A User cannot choose which version of the App they want to use.

When the App is ready for your Users, you should then publish the current version to put it online.

In other words, when clicking this button, the current App configuration for the Architect will become the new version of the App available in production.

🌳 Hierarchy Tab

The sidebar displays the tree structure of Blocks and nested Blocks.

This tree structure allows you to track the number of "levels" that constitute the different nesting levels of blocks, it also serves to easily and quickly find your way around the organization of Blocks, through their title and icon indicating their type.

In this tree structure, you can add and move blocks to organize them. The icons indicate the type of the concerned block and will help you identify the implemented structure.

➕ Adding Blocks

When clicking on the title of a block, you will see three additional action icons appear.

The "+" will allow you to add new blocks after selecting the desired option in the menu that appears.

When clicking on one of these options, the block of the selected type will be inserted as a child block of the block on which you clicked "+".

🔍 Finding Existing Blocks

The search for an existing block will be done through a window in the middle of the page that will allow you to find the concerned block. When clicking on it, it will be added to your tree structure and you can then drag/drop it to assign it to the desired location.

🔗 Block Nesting

It is possible to nest a Block in another, always via drag/drop, we then speak of Parent Block and Child Block, or Parent Block and Nested Block to designate them. Not all Blocks necessarily accept Child Blocks. A Block can have one or several nested blocks.

You can also fold and unfold parent blocks to show or hide nested blocks. It is highly recommended to use this functionality to find your way around and close the block levels you are not working on.

Nesting is possible for all Blocks excepts paragraph.

✏️ Block Management

You can double-click on a block title to rename it, both from the tree structure and from the central panel.

✅ Best Practice: It is advisable to establish a block naming convention very quickly to easily find your way around. It is preferable that this convention be short to identify at a glance what content each block corresponds to.

The button to the right of the "+" allows you to open the block configuration menu. This is where you can assign attributes and their values (essential for child blocks of a choice block), modify visibility conditions (for condition blocks) or generally find settings specific to the block type.

🆔 Block and Attribute IDs

You can access and copy the unique identifiers for blocks and attributes directly from their parameter panels. When you open a block's configuration menu, you'll find a "copy ID" function that allows you to quickly retrieve the block's unique identifier.

This functionality is particularly useful for:

API integrations where you need to reference specific blocks

Advanced configurations that require block identification

Documentation and troubleshooting purposes

Cross-referencing blocks in complex App structures

The same copy ID functionality is available for attributes in their respective parameter panels, streamlining the process of obtaining these identifiers for technical implementations.

🏷️ Attribute Assignment

You can assign to a Block one or several Attributes and one or several existing Values for each Attribute.

It is possible to add as many Attributes and Values as desired for the same Block but two parameters must be considered:

The Attribute and/or the Attribute Value must already exist on the Team

The assignment allows conditioning the visibility of a Block according to the configuration made when it is a Choice Block, contradictory choices or duplicates should be avoided

Learn more here : 🎲 Choice Block

🧙‍♂️ Wizard Tab

The Assistant/Wizard Editor will allow you to configure all the Steps that will take place during the User's journey in the Publication Interface.

We will define the different Steps, the Options they offer, the Attributes they assign, the AI Blocks they execute, etc. The Assistant/Wizard acts as orchestrator of the Blocks to trigger each element at the right moment according to the User's actions.

The step configuration is organized around three tabs: General, Action and Flow.

We will first see the configuration common to different steps, then what is specific to each type.

📋 Common Configuration

🔢 Step Order

By default, the Steps unfold from top to bottom.

You can click on a Step to drag/drop it to the desired location, and thus change the order of your Steps simply.

🔧 General Settings

The different possible step types are Preset options, Input, File upload, Message and End. Each step type has a particular role but configuration elements are common to all types.

For all Step types, you can configure the following elements:

Step Name: This will be the question displayed to the User in the Publication Interface. It should be clear and short.

Description: Additional information provided to the User to clarify the question.

⚡ Action Settings

➕ To Assign

You can add attributes and/or attribute values, they will be assigned to the Publication as soon as the Step is validated.

➖ To Remove

You can add attributes and/or attribute values, they will be removed from the Publication as soon as the Step is validated.

🔄 Blocks to Execute

Allows you to select the AI, Search, File, API or export blocks whose execution must be triggered when the Step is validated.

Logic blocks (Group, Choice, Condition) are executed automatically at each Step to take into account the options entered by the User.

AI blocks (AI, File, Search), Export and API can be assigned manually in the Assistant to be executed at the desired moment.

Learn more here : ⚡ Block Execution

🌊 Flow Settings

It is possible to hide each Step by assigning visibility criteria (according to the presence or absence of certain attributes or attribute values).

Here you can assign a set of conditional criteria to determine when the Step should be visible or not. It is thus possible to choose visibility according to the presence of one or several attributes, one or several attribute values, absence of attributes or values, or combinations of criteria.

💡 For more details on how conditional criteria work, you can consult the article on the condition block which details the possibilities. 🔍 Condition Block

You can also modify for each Step or each Option the default next Step to assign a particular one. This option allows you to skip several Steps without having to hide them with conditional rules.

⚠️ Caution: With this method, intermediate Steps up to the defined Step will be ignored. Make sure that no action necessary for your scenario (block execution, attribute assignment, etc.) is performed only on these intermediate Steps.

✅ Blocking Steps: All steps, regardless of their type, can be set to "blocking" which allows waiting for Block Executions to be completed.

We recommend checking "Wait for everything to be executed" whenever your next action requires content generated by a previous step to be available. In other words, this option ensures that the AI has finished its work on the previous steps.

We invite you to consult the detailed documentation on block execution to properly understand this fundamental concept of Thinkeo. ⚡ Block Execution

🎯 Specific Configuration

Each Step type has specific parameters, which are added to those listed above.

✍️ Input Step

On this Step, the User will have to fill in an input field.

The entered text will become the value of the Text Attribute assigned to the Step, it can be used as a variable in the different Blocks that make up the App. This Step therefore allows retrieving information given by the User to exploit it on the Publication.

The Attribute to assign must be a Text Attribute without existing value, preferably. If it already has possible values, they will be replaced by the entry made by the User.

📝 Preset options Step

This Step will allow proposing to the App User several possible responses, several Options, which will assign attributes and an existing attribute value when the Option is selected.

You will have to choose the response type:

⚪ Radio - Only one possible Option for the User.

☑️ Checkbox - Several possible Options.

📋 Select - Only one possible Option, this format is suitable when Options are very numerous.

In "Change attribute" you can select an existing Attribute having at least one value, all its values will be automatically added as possible Options. You can then modify their title. When clicking on the gear, you will access the Option parameters.

By default, the automatically added Option will assign the Attribute and the value to which it corresponds. You can add attributes or values to assign, to remove, Blocks to execute, etc.

The majority of parameters available for Steps are also available for Options, which will allow you to create specific settings and trigger business logic from Options. The operation therefore remains the same during assignments and executions, triggered upon Step validation.

You can also show or hide the Option with the same possibilities as for Steps.

📎 File Upload Step

This step allows the User to drop one or several files that will feed a files attribute.

This files attribute can be associated with one or several File blocks or Search blocks, you can drop one to several documents during a single step.

You can consult the documentation on the file bloc 📁 File Block or that on the search block 🔍 Search Block to learn more about using the files attribute.

Supported file types and limits:

Supported formats: PDF (.pdf), Word (.docx), PowerPoint (.ppt), Excel (.xlsx), CSV (.csv)

Maximum size per file: 50 MB

💬 Message Step

It serves to inform users by indicating information via the Step Name or Description.

It is highly recommended to use it as the second-to-last Step of your Assistant to invite your App Users to finalize their content, and ensure that all blocks are properly executed by making this Step blocking.

You can also place them occasionally during the journey to trigger Block Executions, while informing the App User of what follows.

This step has an additional option in the "Flow" tab: "Automatically proceed to the next step."

📘 Auto-validation: This option automatically validates the step as soon as block execution is finished. We recommend combining it with the "Wait for everything to be executed" option which will allow automatic scrolling of steps with an informative message.

For example, after a first file upload step by the User and if no other action on their part is required, you can add one or several message steps with these two options active and create a completely automated workflow.

🏁 End Step

When creating an App, an Assistant/Wizard is automatically created and associated with this App. It will contain by default an End Step.

It closes the journey and allows the retrieval of Publications exported to Word, if the concerned Export Blocks have been properly Executed during the previous Step. The End step must be preserved and modified with the message of your choice.

⚠️ Mandatory Step: This Step is mandatory, systematically blocking and is not intended to execute blocks or assign attributes.

🏷️ Attributes Tab

The Attributes tab provides testing functionality by allowing you to assign attribute values directly within the Studio environment.

This tab serves as a debug interface where you can simulate different scenarios without creating actual publications, enabling more efficient App development and testing workflows.

🧪 Testing Functionality

🎯 Attribute Value Assignment - Assign values to attributes directly from the Studio. This functionality allows you to test different attribute combinations and their impact on your App's behavior.

▶️ Block Execution - Execute individual blocks using the "play" button located to the right of the block parameters. This enables targeted testing of specific components within your App.

👁️ Output Visualization - View block execution results directly in the Studio interface, allowing you to verify that blocks produce the expected output with your test attribute values.

🔄 Hierarchical Execution - When a block is executed from the Studio, it automatically executes its child blocks, providing complete testing of nested block structures.

🔍 Debug Interface Features

📤 Output Control

Toggle the "show output" option to control the visibility of execution results from all blocks, helping you manage the information displayed during testing sessions.

📋 Input/Output Inspection

Access detailed input and output data for each block execution, facilitating the identification and resolution of configuration issues.

⚡ Iterative Testing

Test and refine block configurations directly within the Studio without requiring navigation to the Publication Interface for each test cycle.

🎛️ Scenario Simulation

Create different testing scenarios by adjusting attribute values and observing how these changes affect block behavior and App logic.

🔗 API Tab

The API tab provides a dedicated interface for API token management and quick access to API documentation.

This tab centralizes the essential API-related functions within the Studio environment, allowing you to manage tokens and access documentation without leaving your App development workflow.

🔑 Token Management Functions

🆕 Create Tokens - Create new API tokens directly from the Studio. Tokens are automatically displayed in team settings once created.

📋 Copy and Delete Tokens - Copy token values when created and delete tokens that are no longer needed, all from within the Studio interface.

🆔 App ID Access - Copy your App's unique identifier with a dedicated button, useful for API integrations and external references.

📚 Documentation Link - Direct access to the API documentation, providing immediate reference without navigating away from the Studio.

API Scope: Tokens created through this interface include appropriate API scope permissions with automatic verification to ensure proper access control.

⚙️ Settings Tab

This tab will allow you to choose settings for your AI blocks that will apply to the entire App. You can thus set up a global configuration for your AI blocks without having to change them one by one.

You can always manually modify a block parameter to apply a particular configuration to it.

📘 Block Priority: Block-level configuration always takes priority over App-level configuration.

The usable parameters are:

🌡️ Temperature

This parameter controls the degree of variability in model responses. A low temperature makes responses more deterministic and conservative, while a high temperature increases creativity and diversity of responses, but can make them less coherent.

🎯 Top P (Nucleus Sampling)

This parameter limits token choices (words or parts of words) based on their cumulative probability. If Top P is low, the model will choose from the most probable tokens. If Top P is high, it increases the diversity of possible responses by including less probable tokens.

🔄 Frequency Penalty

This parameter penalizes tokens that appear frequently in the generated response. A higher frequency penalty reduces word repetition, making the response more varied.

🆕 Presence Penalty

This parameter penalizes tokens that already appear in the generated response, thus encouraging the model to introduce new concepts. A higher presence penalty increases diversity by discouraging the model from reusing the same words.

🧠 Reasoning

Activates reasoning capabilities for compatible AI models. When enabled, the model adopts a methodical approach with analysis, reflection, and synthesis phases. This is particularly beneficial for complex problems requiring step-by-step analysis, logical reasoning tasks, or cases where transparency of the thought process is important.

These global settings apply to all AI blocks in your App through inheritance, unless overridden at the individual block level.

The possible values will change according to the selected model, the Temperature is adjusted dynamically when you switch from one model to another, remember to check that they correspond to your expectations.

For more information on AI blocks and their configuration, you can consult the dedicated documentation 🤖 AI Block .

🎨 Central Panel

The central panel constitutes the main "page" on which block content will be created and modified until it forms an App.

When clicking on a Block, it is then selected. You can then:

✏️ Edit Content - Enter text, modify or delete content directly in the block.

🌳 Access Hierarchy - Return to the tree structure to add nested blocks or assign attributes.

⚙️ Advanced Options - Click on the "..." in the top right corner of the block to open an additional submenu. This submenu allows opening the Block in a new tab of the Block Editor, removing this Block from its Parent Block or even deleting it permanently.

By choosing "Remove from parent block" the block will not be deleted from the Team but simply removed from the Block where it was positioned, while the "Delete" option is permanent, the block will completely disappear from the Team.

💡 Best Practices and Tips

🛡️ Before the End: Place a Message Step

It is highly recommended to add a Message Step with the blocking option checked between your end step and the previous step that executes (normally) your entire App.

This ensures that all planned processing has been performed, that AI content generation is complete and that the App User has been able to finalize the Publication content before validating the Step.

📤 Add Export Block Execution on the Second-to-Last Step

Block Execution always happens upon Step validation, so Export Blocks should be Executed on the second-to-last Step of the Assistant/Wizard so that the final content of the publication is exported.

🔄 How to Restart an Export

Currently, to trigger Export Block Execution again, you must go back to a previous Step and change an Option or an entry in a Text field then validate the Step for the journey to adjust and create new documents during Export.

📊 Organize Your Step Order

Consider the journey as a continuous flow, prioritize hiding questions to implement your App's logic.

The possibility of assigning a default Step to a Step or Option should occasionally serve specific cases, abusing this functionality will greatly complicate the organization and maintenance of your Assistant/Wizard.

If you have trouble visualizing, use tools like Miro or Whimsical to draw your question tree structure.

🎯 Key Takeaways

The Studio provides a comprehensive environment for App creation where:

Six specialized tabs organize all configuration, testing, and API management aspects

Visual hierarchy management through drag-and-drop block organization

Powerful wizard system orchestrates user journeys and AI executions

Integrated debug mode enables direct testing and iteration within the Studio environment

API management interface centralizes token and integration management

Global AI settings streamline configuration across all blocks

Central editing panel provides direct content manipulation

This unified interface encompasses the complete App development workflow from initial creation to testing and API integration.

🎯 Overview#

📱 App Tab#

🏷️ Logo and App Name#

📝 Description#

🔐 Restrict Access To#

🚀 Publish Current Version#

🌳 Hierarchy Tab#

➕ Adding Blocks#

🔍 Finding Existing Blocks#

🔗 Block Nesting#

✏️ Block Management#

🆔 Block and Attribute IDs#

🏷️ Attribute Assignment#

🧙‍♂️ Wizard Tab#

📋 Common Configuration#

🔢 Step Order#

🔧 General Settings#

⚡ Action Settings#

🌊 Flow Settings#

🎯 Specific Configuration#

✍️ Input Step#

📝 Preset options Step#

📎 File Upload Step#

💬 Message Step#

🏁 End Step#

🏷️ Attributes Tab#

🧪 Testing Functionality#

🔍 Debug Interface Features#

🔗 API Tab#

#

🔑 Token Management Functions#

⚙️ Settings Tab#

🎨 Central Panel#

💡 Best Practices and Tips#

🛡️ Before the End: Place a Message Step#

📤 Add Export Block Execution on the Second-to-Last Step#

🔄 How to Restart an Export#

📊 Organize Your Step Order#

🎯 Key Takeaways#