Workspaces: Project Directories
Workspaces in Querlo Studio function similarly to directories or folders on your computer, but with specialized capabilities designed specifically for managing conversational flows. They are the primary way to organize and group structurally related projects or conversational flows at the team level.
Why use Workspaces?
Workspaces provide a unified environment for your chats, giving you four key architectural benefits:
Grouping Project Chats: Keep all the chatbots and conversational flows for a specific client, department, or campaign neatly organized together within a single location.
Connecting Between Listed Chats: Easily establish connections and seamless flow redirects between the different chats listed within the same workspace. This allows you to build modular sub-flows and keep individual chat files clean and maintainable.
Common CSS Styling: Define global CSS styles and color themes at the workspace level. These themes automatically apply to every chat embedded within the workspace, ensuring a consistent visual identity without deploying repetitive code blocks.
Common Variables Resumption: Share global variables, conversation state, credentials, and API connections across multiple chats within the workspace. When a user traverses from one chat sequence to another within the same workspace, their session context properties are resiliently resumed and maintained.
Session resume options
In Workspace Edit, you can choose how session continuity works when users move across chats in the same workspace:
- Reset session: Start each connected chat as a new session. No previous conversation state is resumed, and the chatbot does not place any cookie for session resumption.
- Variables only: Resume only stored variables (for example user attributes or business data), but not full conversational progression/history.
- Full resume: Resume the complete session context, including variables and conversational progression, so users continue where they left off.
Privacy and GDPR note
If your compliance policy requires no session persistence cookies, use Reset session.