MIA
Go deeper

Roles and rights when building together

Building together only works if you can decide exactly who may do what. That's why everything in Mia Connect is a deliberate choice — and the door is closed by default.

Updated 2026-08-09 · Working together

Four roles, from watching to owner

Every participant in a build session has a role:

  • Views — sees the queue and the preview, but sends nothing in.
  • May build — sends in build requests that are executed on your Mia.
  • Co-manages — may also invite members and adjust roles.
  • Owner — that's you: the app lives on your Mia and you always have the final say.

Changing or revoking a role is possible at any moment, per person.

Access: per person or open to your connections

You choose per app how people get in. Per person means: only those you explicitly invite take part. Open to my connections means: anyone you're connected with can join, with a default role you pick in advance — handy for an app your whole team thinks along on.

Exposure: just that one app by default

A build session gives access to exactly one app — not to your Mia. Two things are off by default and only switched on deliberately:

  • Stored data — may Mia also look into the app's stored data while building?
  • Running commands — may anything be executed on the server during the build?

Important to know: these boundaries are not a polite agreement. They are technically enforced at the moment Mia executes the work — a request that falls outside them simply cannot run.

Frequently asked questions

Can someone with the co-manages role take over the app?

No. Managing is about members and roles within the session. The app itself lives on your Mia and remains yours — ownership is not transferable through a role.

What happens when I lower someone's role?

It takes effect immediately. They get a notification and their possibilities adjust right away — work already in the queue is finished neatly by Mia.

Why is stored data off by default?

Because it may contain customer or personal data. Building on an app's looks and behaviour works fine without it — you only grant more access when it's truly needed.