Tiet · Studio and Tiet · Agentic
Tiet · Studio and Tiet · Agentic are the build-and-automate side of Tietai, run by the platform's workflow engine. In the application they appear as Platform (projects, connectors), Tiet · Studio (workflows) and Tiet · Agentic (agents and AI governance).
Where they live in the sidebar
| Group | Item | Sub-items and purpose |
|---|---|---|
| Tiet · Hub | Platform | Monitor (platform health), Projects (group agents, workflows and tools), Connectors (saved connections to external systems), Egress policy (which external hosts agents and tools may reach), Environments (named deployment environments, with tabs Environments, Routes, Agents & workflows, Trusted sources, Approvals and Retention) |
| Tiet · Studio | Workflows | Workflows (the builder and your workflow list) and Monitor (runs, logs and traces) |
| Tiet · Agentic | Agents | Agent Workspace (chat with and run agents), Agents (the agents page), Monitor (agent activity and traces) and Reviews (proposals waiting for a human decision, across all agents) |
| Compliance | Systems, Policies, Gate, Watch, CAPA, Audit for AI governance |
The Agents page has these tabs: Agents, Agent Graphs, Agent Catalog, Models, Tools and Skills.
A typical way to work
- Pick or create a Project under Tiet · Hub → Platform → Projects. Creating an agent requires an active project.
- Add the Connectors the work needs under Tiet · Hub → Platform → Connectors.
- If the work needs reasoning or tools, create an agent under Tiet · Agentic → Agents → New Agent. The dialog asks for a name, a type, a description and the project. You then set instructions and tools in the agent designer.
- Build the workflow under Tiet · Studio → Workflows → New Workflow.
- Run it and inspect the result under Tiet · Studio → Workflows → Monitor.
- Move it between environments. In the Builder, the Deploy menu sets a status and exports JSON or YAML. Environments, promotion routes and approvals are managed on Tiet · Hub → Platform → Environments. See Environments and promotion.
Concepts such as workflow statuses, ports and agent graphs are explained in Key Concepts.
Permissions
Access is permission-based. Each sidebar item needs permissions, for example:
- The Platform, Workflows and Agents items need
access:hydra. - Projects needs a project list or read permission. Connectors needs connector read or manage.
- Workflows needs a library, builder or pipeline permission; its Monitor needs a monitor permission.
- Compliance needs a compliance read, manage, review or audit permission.
If a user can open Studio but not create agents or workflows, check their roles, groups and direct grants in Admin Console → Organization → Roles & Permissions.
Apps versus Studio and Agentic
Use Tiet · Hub → Apps for ready-made clinical applications. Use Tiet · Studio and Tiet · Agentic to build:
- an agent, or an agent graph with tools
- a data-processing workflow
- a scheduled automation
- an integration between systems
Something unclear? Send documentation feedback by email.