Console Tour
Find Studio, Apps, Observe, Settings, and Billing in the PromptRails Console.
Best for
New workspace members choosing between Teams and Console
Console is the workspace for building and operating agents. Use it to configure runtime behavior, test changes, publish an app, and inspect what happened in a run. For assigning work to AI employees on boards and in conversations, start with Teams.
Open a workspace
After signing in, choose a workspace from the hub. Each workspace keeps its agents, apps, data, and member access together. Check the workspace selector before creating resources or changing configuration. The product switcher takes you to other PromptRails products, including Teams.
Navigate the workspace
| Area | What you do here | Learn more |
|---|---|---|
| Overview | See recent activity and choose where to start. | Quickstart |
| Studio | Work with agents, prompts, data sources, knowledge, and tools. | Agents, Prompts, Knowledge Sources |
| Apps | Build hosted web apps, presentations, and site extensions. | Apps |
| Observe → Trace explorer | Inspect runs and spans; open the dashboard, sessions, and Quality. | Tracing, Sessions, Quality / Evaluations |
| Observe → Approvals | Review executions paused before a gated call. | Approvals |
| Observe → Costs | Review model usage and execution costs. | Cost Tracking |
| Settings | Manage credentials, API keys, members, notifications, and workspace controls. | Workspace Management |
| Billing | Manage the plan, balance, and billing details. | LLM Gateway |
Within Observe, use the icon rail for Overview, Trace explorer, Costs, Sessions, End users, Quality, and Approvals.
Settings and Billing require workspace admin or owner access. Your role can also limit individual actions elsewhere in the product. See Workspace members and roles.
Build in Studio
Use the Explorer to open a resource. Agents, prompts, data sources, and MCP tools share the Studio workspace, so you can inspect their relationships while building. Open the relevant resource’s settings, version history, or playground when you need to edit, compare, or test it.
Prompts hold content and template inputs. Agent versions hold runtime settings such as the model, sampling, tools, sub-agents, output schema, budget, and approval policy. Save and test a version before promoting it for callers.
Inspect a run
After running an agent, open Observe → Trace explorer. Inspect the timeline and individual spans to understand model calls, tools, timing, tokens, cost, and failures. Check Observe → Approvals if the run is waiting for a human decision. Sessions group conversational work; evaluations help compare behavior across repeatable cases.
Use the Assistant
Open the Assistant to describe a workspace change or ask about the current resource. It can use workspace tools, so review the resulting configuration and run the same checks you would after a manual change.
Continue with the Console quickstart, or switch to Teams to assign the agent work as an employee.