Workspace tools and scope
Understand the Studio left rail, workspace-wide resources, and the boundary between a workspace and a project.
Studio always operates inside an active personal, team, or organization workspace. The workspace is the membership, permission, collaboration, and shared-resource boundary. A project is a code and workflow boundary inside that workspace. Changing the active workspace changes the projects, people, conversations, tasks, and resources available to you.
Home
Home lists projects available in the active workspace. Create an empty project, import a Git repository, or open an existing project. A registered repository can own one root project and nested projects for packages or services. Opening a project reveals its project tabs; it does not change the active workspace.
Tasks
Tasks is workspace planning, not a project issue file or a workflow. Task Spaces hold work items and planning views, and a task may link to several projects, workflows, or pull requests. See Tasks.
Otto
Otto contains AI assistant sessions. A session is private when created and is bound to one or more selected projects. Invited members can collaborate in that session, but ordinary Chat does not list assistant sessions. See Otto.
Chat
Chat contains human workspace, group, and direct conversations. Messages can carry links to workflows, tasks, and Design Docs so discussion stays connected to its source without copying that resource into Chat. See Chat.
Design Docs
Design Docs is collaborative workspace content for technical decisions and review. A document may be workspace-wide or project-scoped. It supports Markdown, HTML, or plain text, immutable revisions, pinned review comments, and an optional revocable public link.
Design Docs is not the same as a project's Documentation tab. Project Documentation edits repository files; Design Docs stores collaboration revisions separately. Publishing a community guide is another explicit review step and never happens because a document was saved or shared.
Data Tables
Data Tables opens the workspace table browser. Select Global for a table reusable across projects or select one project for isolated project data. The project must attach a global table before its workflows can use it. See Data tables.
Nodes
Nodes browses the workspace node catalog. It includes built-in nodes and nodes supplied by installed plugins. A project's Nodes tab shows the catalog in that project context; adding or editing a source-backed node still follows the project's source and revision rules.
Variables
Variables manages reusable configuration for the active personal, team, or organization workspace. Shared variables are not automatically available to every project: attach only the names a project needs. See Variables and secrets.
Community
Community discovers reviewed public guides, papers, blog posts, and workflow templates. Community content is a publication surface, not trusted project state. Importing a workflow template creates a project copy; later publication edits do not silently rewrite it.
Marketplace
Marketplace manages workflow plugins in the workspace library. Installing a plugin makes it available for reuse; use the project's Plugins tab to attach it to the project that will execute its nodes. Review its code, dependencies, requested credentials, and runtime effects before installation. See Nodes and plugins.
Footer tools
Runs shows execution history across the active context. Settings manages workspace and environment configuration. Profile manages your identity. Administrative pages appear only when the current role has their permissions. A missing tool can also mean the deployment does not provide that capability.