Work Process — Who Does What and When
This document outlines how to run Studio in your organization. Since anyone can build apps, you need rules that separate builders from users — otherwise things get messy fast.
The tutorial is "build and deploy one app for the first time." This document is "multiple people building and using apps continuously."
Three roles
| Role | Responsibility |
|---|---|
| admin | Environment setup, user management, AI provider, deployment targets |
| builder | Build and deploy apps (default at account creation) |
| viewer | View deployed apps |
Create accounts and assign roles in Settings → User Management → Change initial password.
The default is builder, so anyone can build apps if you don't assign roles. As apps grow,
nobody knows who built what. Give viewer to people who only view.
Full workflow
Arrows crossing lanes mark handoff points.
1. Deployment — Set these before building
| Step | Task | Owner |
|---|---|---|
| 1 | Install → One-line install | admin |
| 2 | Change default password → Change initial password | admin |
| 3 | Connect AI provider + test connection → Settings | admin |
| 4 | Lock build standards — stack, layout, dependency lock | admin |
| 5 | Create accounts and assign roles | admin |
| 6 | Pilot app build | builder |
If you leave build standards open, different stacks appear in different apps. Turn on dependency lock and enforce layout rules — output stays consistent → Settings (admin).
2. Building apps — From requirement to deployment
| Stage | Task | Deliverable |
|---|---|---|
| Requirements | One screen = one sentence — break it down | Requirement statement |
| Creation | Start from home with a sentence → Create app from home | Draft screen |
| Refinement | Improve by talking in Studio → Builder | Complete screen |
| Review | Requester views it directly | Sign-off |
| Deployment | Deploy drawer → Catalog and sharing | App URL |
| Distribution | Give URL to field | — |
Conversation content may be stored in app code. If you need keys, ask admin → Secret management.
3. Operations — Regular tasks
| Frequency | Task | Owner |
|---|---|---|
| Daily | Check watcher alerts → Watchers and alerts | Field |
| Weekly | AI usage and deployment failures | admin |
| Monthly | Clean up unused apps, backup recovery drill | admin |
| Quarterly | Rotate keys → Change passwords and API keys | admin |
Watcher intervals might be too short or "vision self-validation" is on during large builds. Check the Statistics screen first.
4. Build field knowledge
Don't rewrite the same instructions every time. Register repeated rules as skills — they auto-apply to future builds → Field skills.
| What to register | Example |
|---|---|
| Screen conventions | "Company logo at top of every screen" |
| Color rules | "Utilization below 80% = red" |
| Terminology | Equipment abbreviations your field uses |
Common trouble spots
| Symptom | Usual cause |
|---|---|
| "Too many apps, can't tell them apart" | No naming rules + unused apps not deleted |
| "Every screen looks different" | Build standards not enforced |
| "AI costs jumped suddenly" | Watcher intervals too short, vision self-validation left on |
| "App builder left and we can't fix it" | Apps are assets — assign an owner and do handoff |
| "Deployed fine but field can't open it" | App listener port blocked in firewall |
Related docs
- Tutorial — Build and deploy your first app
- Settings (admin) — Build standards, AI providers
- App catalog and sharing
- Backup and restore