A project team: a colleague works on the mini app under their own number

How to invite a colleague

1. 1

   Open the team window

   The Team button in the editor’s top bar, More → Project team, or the people icon in the project’s row on the projects screen.

2. 2

   Enter the number and invite

   If the person already has an account, the project shows up in their Shared with me at once, and an invitation message arrives in their messenger.

3. 3

   No account yet — the invitation waits

   It is marked “Waiting” in the list. Copy the invitation with the button in the window and forward it: as soon as they sign in with that number, the project appears for them on its own.

Editing in turns, not at the same time

There is no real-time co-editing like in Google Docs. If the project was saved from somewhere else while you had it open, the editor won’t overwrite the other person’s work: it shows that the version changed and asks which to keep. Your copy isn’t lost — it can be saved as a separate project.

In practice that means agreeing on turns: the marketer edits screens in the morning, you in the evening. Nothing is lost silently, but there won’t be two cursors on one canvas.

The editor team and helpers inside the app are different things

A teammate works in the editor: on screens, the project’s catalog, publishing, submissions and payments. The records visitors leave in the app’s tables stay hidden from them — only the owner sees those. There is also a second, narrower access that existed before: the app’s data editors. They change catalog, schedule or price rows right in the published app from a phone and never touch the project itself. Replies to visitors in Chat can also come from someone the owner made admin of that table.

Pick by the job. An administrator who only changes prices and checks bookings is fine with data access in the app. Someone who builds and ships new screens needs a seat on the team.

A teammate with their own AI assistant

A teammate can connect Claude, ChatGPT or Cursor to their account with the Shared projects permission. The assistant edits and publishes the shared project but doesn’t see visitors’ data tables: data permissions are granted only by the owner, and only for their own apps.

Taking access away

The icon next to a person in the team window removes them from the project, and access closes at once. A teammate can also leave: the Leave project button in the same window or on the projects screen. The owner’s project stays as it was.

The limits, stated plainly

• No simultaneous editing: saving over someone else’s changes opens a conflict window.
• Seats are limited by the owner’s plan. When they run out, the next invitation offers a plan with more seats.
• Records in the published app’s tables — personal orders, carts, rows added from a phone — are not visible to a teammate: they hold every visitor’s personal data and are shown to the owner only. Form submissions and payments a teammate does see.
• A teammate can’t delete the app or change the bot, address, domain or till. If another person needs to do that, it has to be their own account and their own project.

Questions people ask

Can I give a colleague access to a mini app without sharing my password?

Yes. The colleague signs in to the builder with their own phone number, and the project appears under Shared with me. They need neither your password nor your account.

How many people can I invite?

One teammate on Trial and Start, three on Pro, ten on Studio. A seat is a person: one teammate in three of your projects takes one seat.

Does a teammate pay separately?

No. Everything they do in your project runs on your plan: publishing, storage, AI builds.

Can two people edit a project at once?

No, only in turns. If two people save over each other, the editor shows a conflict window and overwrites nothing silently; the second copy can be saved as a separate project.