Sharing your projects

There are six ways to share a Floot project: pass on the preview link your AI assistant gave you, add collaborators, send a development preview, publish the app privately for people you invite, send the whole project to another account, or make the project public.

Share the preview link your AI gave you

Every preview link the Floot connector returns already carries a view-only token in its query string. This is the normal way to show work in progress to someone who does not need an account.

• It opens with no login, so it works in a phone browser or an in-app webview
• It is scoped to one project, and expires after 7 days
• The holder can look at the project and interact with the running app, but cannot change files or touch your account
• A single link cannot be revoked before it expires, so share it only with people you would show the project to. To close every preview link of the project at once, turn on Only allow internal publish
• Share it exactly as your assistant returned it — stripping the token turns the link into a sign-in prompt
• Lost it, or the 7 days ran out? Ask your assistant for the preview link again and it mints a fresh one

Add collaborators

Give other people edit access to your project while you keep ownership. Collaborators can always edit — there is no view-only level; to let someone use the app without touching the project, publish it privately and invite them instead. This needs a paid plan, and only the project owner can add or remove people. There is no MCP tool for it — collaborators are managed on floot.com.

1. 1

   Open the project menu

   Click the project name dropdown in the top-left, next to the Floot logo, then Collaborators. The + next to the avatars in the top-right of the project opens the same dialog.

2. 2

   Enter their email

   Any email address works, whether or not that person has a Floot account yet.

3. 3

   They're in, or invited

   If they already have a Floot account, access is granted right away, and Floot emails them at that address. The subject line reads "<your name> added you to <your project> on Floot", and the message has an Open Project button that opens the project on floot.com under their own account.

   If they don't, Floot emails them an invite instead. The subject line reads "<your name> invited you to <your project> on Floot", and its Sign in to Floot button takes them to sign-in and then to the project. Once they create an account with that same email address, they are added to the project automatically. Until then they are listed under Invited in the Collaborators dialog, where the X cancels the invite.

What to know

A collaborator who wants to work on the project from their own MCP client needs their own paid Floot plan — opening a shared project over MCP is refused otherwise — and their build actions come out of their own daily allowance, not yours. Image generation is the exception: it always spends the project owner's credits.

• There are two roles, owner and collaborator. A collaborator can edit, publish and unpublish, change data, and manage integrations, domains and schedules. Only the owner can delete the project, manage collaborators, or send the project or a development preview.
• You can remove a collaborator at any time in the same dialog, which revokes their access immediately.
• An invite is tied to the exact address you typed. If they sign up with a different email, the invite does not reach them: cancel it and add their new address. Entering the same address again sends the invite email again.
• Changes made by your assistants show up live for everyone who has the project open — no refresh needed. There is no edit lock, so agree on who is working on what.
• A collaborator who opens the dialog sees "Only project owners can manage collaborators" — they can edit the project but not change who else has access.
• Collaborators get full access to the project's data and integrations, so only invite people you trust with them.

Send a development preview

Show a client or a tester what you are building without giving them the project. Open the project name dropdown in the top-left, then Send Development Preview. This needs a paid plan and is shown only to the project owner.

• Up to 20 recipients at a time, and 50 in any 24 hours
• Each recipient gets their own link by email
• To open it, they must enter their own email address to verify who they are
• Links expire after 7 days
• If an email fails to deliver, you can copy that person's link and send it yourself — they still have to verify their address

Publish the app privately

To let specific people use the published app — a team tool, a client preview, a beta — without making it public or giving them the project, publish it internally. Open Publish, choose the Internal publish tab, add people by email, and click Publish internally. They get an invite, sign in with a Floot account on the address you invited, and can use the app but not open the project. Free accounts can invite 5 people across all their apps and paid plans 20; to invite more, contact support@floot.com. See Publish privately.

Send project to another account

Copy a project to a different Floot account. This needs a paid plan and is shown only to the project owner. You can send at most 5 projects in 30 minutes and 10 a day.

When to use it

• Handing a finished project off to a client
• Moving a project to a team or company account
• Consolidating projects under one account

How it works

1. 1

   Open Send project

   Click the project name dropdown in the top-left, then Send project.

2. 2

   Enter the destination email

   The recipient does not need a Floot account until they accept. Optionally add a message, or charge them credits for the project — the smallest charge Floot accepts is 6,000 credits.

   If the project has a Floot database, choose under Database whether they get Copy schema and data or Schema only (empty tables).

3. 3

   They accept or decline

   Floot emails a link. If they accept, they receive a full copy — code, database, and integrations — but not your API keys, which they will set up themselves.

   The copy is made when they accept, from the project as it is at that moment. Anything your app records after that stays in your project only.

4. 4

   What can block an accept

   The recipient needs a free project slot — free accounts are capped at 5 projects — and, if you set a credit charge, enough credits to cover it. If either check fails the accept is refused and the invitation stays pending, so this is worth checking before you go looking for a bug.

5. 5

   Credits change hands

   If you set a credit charge, the recipient pays it and you receive that amount minus a 5,000-credit fee — so at the 6,000-credit minimum, 1,000 credits reach you.

What does not come along

The copy arrives unpublished. The floot.app address, custom domains, app store connections, collaborators, and the project's checkpoints and history stay with your project, so the recipient publishes and adds the domain on their side. See what a copy gets for the full list.

To hand over a live address, remove the custom domain and unpublish on your side, then have them publish under the same floot.app name straight away and add the domain to their project. The app is offline in between, and a released name can be taken by anyone, so do both steps together.

Send project is how a project moves from one account to another. If what you want is the same account under a different email address, change the account email instead.

Make a project public

Let others view your project's source code and its activity record — the running log of the work done in the project, including everything your assistant did — and use it as a starting point for their own. Making a project public is free on any plan.

1. 1

   Open Project Settings

   Click the project name dropdown in the top-left, then Project Settings.

2. 2

   Turn on Make project public

   Under Project Visibility, turn on the Make project public switch. There is no list of visibility values to pick from — it is one toggle, and you can turn it back off at any time.

What happens

• Others can view your source code and that activity record, but they cannot edit your project
• Other Floot users can duplicate it as a starting point — duplicating someone else's project requires a paid plan on both sides, so this only works while you are on a paid plan too
• Your published app URL is unchanged — this affects the project, not the live app
• You keep full ownership and can go private again whenever you want

When to use it

• Sharing a template or example with the community
• Open-source work you want others to learn from
• Showcasing a build in your portfolio

Which option should I choose?