# How to navigate the Agentic Studio interface ### Overview Agentic Studio is organized around the Digital Worker lifecycle. The platform's main areas correspond to the stages a Digital Worker moves through, from initial creation and configuration, through testing and evaluation, to deployment and ongoing monitoring. This article describes what each area of the platform contains and when to use it. ### Digital Workers The Digital Workers area is the starting point for all development work. From here, users create new Digital Workers, import existing configurations from the marketplace or saved templates, and access the workspaces where individual workers are configured. Each Digital Worker has its own workspace, which contains the full set of configuration options: instructions, tools, skills, triggers, connectors, and settings. This is where a Digital Worker's behavior is defined and refined before it moves to testing. ### Compose The Compose area is where a Digital Worker's core configuration is built and edited. It contains the instructions that define how the worker behaves, the tools it can call, the skills it applies, and the triggers that initiate its activity. Settings such as reasoning effort, verbosity, human-in-the-loop behavior, and concurrency are also managed here. Changes made in Compose apply to the draft version of the Digital Worker. The draft is the active working state, editable, testable, and separate from the published production version. ### Evaluate The Evaluate area provides a dedicated environment for validating Digital Worker behavior before deployment. It supports two modes of testing: interactive testing for individual scenarios and ad hoc validation, and dataset-based testing for broader, repeatable evaluation across many cases. Interactive tests allow users to engage with a Digital Worker directly through a conversational interface, observe how it responds, and assess whether its behavior matches expectations. Evaluation signals, including accuracy, relevance, and helpfulness, are surfaced for each interaction. Dataset testing allows users to run a saved collection of test cases against the Digital Worker and review aggregate metrics across the full set. Datasets function as persistent evaluation assets that can be reused as the Digital Worker evolves, supporting regression testing and release readiness checks. ### Deploy The Deploy area manages the release of Digital Workers from test to production. Once a Digital Worker has been validated, the release process moves through two steps: publishing a new version and pushing that version to production. Publishing creates a versioned, release-ready snapshot of the current draft. Pushing to production promotes that snapshot into the live environment, where the Digital Worker becomes available for active use. The version history created through this process supports auditability and, where needed, rollback. ### Monitoring and Analytics The Monitoring and Analytics area provides visibility into how Digital Workers are performing in production. It covers operational metrics such as conversation volumes, completion rates, and user feedback, as well as quality metrics including compliance scores and conversation quality evaluations. Knowledge dashboards surface trending topics and common queries, giving teams insight into what users are asking and where patterns are emerging. Custom dashboards can be configured for teams with specific reporting needs. ### Connectors The Connectors area is where integrations with external systems are set up and managed. Connectors provide authenticated access to the enterprise applications, knowledge sources, databases, and APIs that Digital Workers rely on. A connector is configured once and can be reused across multiple tools and workers within the same workspace. --- # 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://kb.theloops.io/agenticstudio/resource-library/hidden-fundamentals/how-to-navigate-the-agentic-studio-interface.md?ask= ``` 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.