Workspace Process
This document describes how an organization should run Studio. Because it's a tool that allows anyone to create apps, without rules that separate the creators from the users, things quickly become chaotic.
While a tutorial is about "building and deploying a single app for the first time," this document is about "how multiple people continuously build and use apps."
There are three roles
| Role | Responsibility |
|---|---|
| admin | Environment settings, user management, AI providers, deployment targets |
| builder | Creates and deploys apps (default when creating an account) |
| viewer | Views deployed apps |
Accounts are created and roles are assigned in Environment Settings → User Management → Initial Password Change.
Since the default is builder, simply creating accounts gives everyone the ability to make apps. As the number of apps grows, it becomes impossible to know who made what. Set those who only need to view to viewer.
Overall Flow
Where an arrow crosses lanes is the handover point.
1. Introduction — What to Decide Before Building
| Step | Action | Owner |
|---|---|---|
| 1 | Install → One-Line Installation | admin |
| 2 | Change the default password → Initial Password Change | admin |
| 3 | Connect AI provider + connection test → Environment Settings | admin |
| 4 | Finalize the build standard — lock stack & layout | admin |
| 5 | Issue accounts & assign roles | admin |
| 6 | Build the first trial app | builder |
If build standards are left open, apps will be built with different stacks by different people. Enabling dependency locking and layout convention enforcement keeps results consistent → Environment Settings (Admin).
2. Creating an App — From Requirement to Deployment
| Phase | Action | Output |
|---|---|---|
| Requirement Definition | Break down into one screen = one sentence | One-line requirement |
| Generation | Start from a sentence on the home screen → Create App from Home | Draft screen |
| Refinement | Refine via chat in the Builder → Builder | Final screen |
| Review | The requester inspects it directly | Confirmation |
| Deploy | Deployment drawer → Catalog & Sharing | App address |
| Share | Provide the address to the field | — |
The conversation may be stored in the app code. If a key is needed, request it from the admin → Secret Management.
3. Operations — Recurring Tasks
| Cadence | Action | Owner |
|---|---|---|
| Daily | Check watcher alerts → Watchers & Alerts | Field |
| Weekly | Check AI usage & failed deployment count | admin |
| Monthly | Clean up unused apps, backup recovery rehearsal | admin |
| Quarterly | Rotate keys → Password & API Key Changes | admin |
The likely cause is either watcher intervals being too short, or a large build running with "Vision Self-Verification" enabled. Check the Statistics screen first.
4. Building Field Expertise
Rewriting the same instruction each time is wasteful. Register recurring rules as skills so they're automatically applied to future generation → Field Skills.
| Examples of what to register | Example |
|---|---|
| Screen conventions | "Company logo on top of every screen" |
| Color rules | "Red for utilization below 80%" |
| Terminology | Field's equipment abbreviations |
Common Points of Friction
| Symptom | Typical Cause |
|---|---|
| "Too many apps, I can't tell what's what" | No naming rules + unused apps not removed |
| "Screens look different from person to person" | Build standards not enabled |
| "AI costs suddenly increased" | Watcher intervals or vision self-verification |
| "The person who made the app left and no one can fix it" | Apps are assets — assign an owner and hand over |
| "Deployed it, but it won't open on the field" | App listener port blocked during port-connection installation |
Related Documents
- Tutorial — Build and Deploy Your First App
- Environment Settings (Admin) — build standards, AI providers
- App Catalog & Sharing
- Backup & Recovery