Who should build in Miiwa—and who should run the finished tools?
In Miiwa, admins govern the platform, workspace builders author native workflows, and workspace users consume assigned Miiwa Agents without access to the underlying graph, prompts, keys or routing.
Miiwa is built around a deliberate separation: a small group designs the system, while everyone else uses the finished capability. That separation is enforced through three access layers—Admin, Builder and User—not left to a convention in a prompt or an internal handbook.
Miiwa has three access layers
- Admin
- A platform administrator can author workflows and manage the control layer around workspaces, access, services, integrations and operations.
- Builder
- A workspace user with builder access can create and maintain native workflows and can also consume finished tools, without receiving platform-wide governance access.
- User
- A workspace user runs the Miiwa Agents and domain tools assigned to them. They do not enter Native Studio or inspect prompts, graphs, provider routing or trigger secrets.
The right person to build is therefore not simply the most technical person or everyone with an AI idea. It is a trusted domain or technical specialist who understands the process, the permitted data and the intended output, and who has been given Builder access inside the relevant workspace.
The access model follows Miiwa’s four product layers
| Layer | What happens in Miiwa | Primary access |
|---|---|---|
| Authoring | Native Studio and Miiwa Architect turn business intent into graphs, blocks, variables, interfaces and versions. | Admin and Builder |
| Runtime | The native workflow engine executes the graph, carries variables, pauses, resumes and persists run state. | System-managed |
| Delivery | Published Miiwa Agents expose guided inputs, progress and usable outputs without exposing the workflow internals. | User, Builder and Admin when assigned |
| Control | Service Router, workspace configuration, integrations, run history, AI Operations and governance surround the runtime. | Primarily Admin |
What does a Miiwa Builder actually build?
- A graph-based workflow in Native Studio, composed from typed blocks and edges.
- A guided input experience using User Input and reusable input-field definitions.
- A variable contract that carries approved user and system context into downstream blocks.
- Model, knowledge, scraping, transformation, integration and asset steps required for the outcome.
- A delivery surface that turns the result into a useful agent response, structured output or rendered asset.
- A version that passes Miiwa’s publish-readiness checks before it becomes a deployment.
What does a Miiwa User receive?
A user receives a finished tool. A published Miiwa Agent can be enabled for a whole workspace or explicitly allowed or denied for one user, then pinned and ordered in the user experience. When the agent needs live information, the user answers a guided form; the runtime binds those answers to variables and continues the workflow.
The user sees the input requested for the task, the relevant progress state and the resulting output or asset. They do not need to understand block types, moustache variables, model identifiers, provider keys, MCP configuration or the workflow graph.
Why is the workspace the governing boundary?
Every Miiwa workspace is its own operating environment. Memberships, projects, workflow versions, deployments, provider configuration, integrations, assigned agents, runs and outputs are scoped to that workspace. Giving someone Builder access changes what they may design inside that boundary; it does not give them an unscoped view of other workspaces.
Choose access from the responsibility
| Responsibility | Miiwa access |
|---|---|
| Operate platform governance, workspace controls and shared services | Admin |
| Design or maintain the workflow logic and its user-facing interface | Builder |
| Run an approved tool and use its output | User |
| Give one person access to one finished capability | User assignment—not a Builder promotion |
Miiwa does not make every employee an agent builder. It gives trusted admins and builders a powerful authoring system and gives everyone else the simpler, safer product: finished Miiwa Agents.
Common questions
- Can a domain specialist become a Miiwa Builder without being a developer?
- Yes. Builder access is a product permission, not a job title. A domain specialist can use Native Studio and Miiwa Architect when they are trusted to design the process and work within the workspace’s data, service and publishing boundaries.
- Can a normal Miiwa User see an agent’s prompt or workflow graph?
- No. The user experience exposes the guided inputs, relevant run state and delivered output. Prompts, variables, block configuration, provider routing, trigger secrets and graph internals remain in the authoring and control layers.
- Does Builder access make someone a Miiwa platform administrator?
- No. A workspace Builder receives authoring access and can consume finished tools, but platform governance remains an Admin responsibility. Miiwa derives those as separate access layers.