How do I share an AI-built app? Privately, with one team login

Blog · August 18, 2026 · Rich Chetwynd

How do I share an AI-built app? Privately, with one team login

How to share an app you built with AI: deploy it behind one team login and send a link that only the people you invite can open. No public URL, no emailed files.

Short answer: To share an AI-built app, deploy it to a host that gives it a real web address behind a login - like Croft - then invite your team by email. They open the link, sign in once, and use the app. There’s no public URL and no accounts for strangers.

The trouble with an app your AI built in the chat is that there’s nothing to send. A screenshot isn’t the app. A file only works if the other person can run it. And a raw public link would let anyone in. Sharing something real, but keeping it private, needs a proper home.

How to share it with your team

  1. Deploy the app to your croft. Connect an assistant and ask it to deploy the app. How to connect →
  2. Invite your people. Add them by email on the People page and choose which apps each can open. They sign in with a passkey through your croft’s enterprise single sign-on.
  3. Send the link. It’s a real URL they open in a browser, on any device - but only the people you invited can get past the login.

That’s the whole job: one deploy, one login for the team, one link.

The quick ways to share an AI-built app each break somewhere:

  • A preview or artifact in chat lives in your conversation. Colleagues can’t open it on their own, and there’s usually no saved data behind it. See what an AI artifact is and how to turn one into an app.
  • A screenshot or an emailed file means everyone ends up with a different copy, and every update is another attachment.
  • A public link lets anyone who finds or is forwarded the URL open it, which is a poor fit for internal numbers, client data or team tools.

A shared app needs three things: a link people can open, a database that keeps the data in one place, and a login so only your people get in.

Share from Claude, ChatGPT or Cursor

It doesn’t matter much which assistant built the app. Connect it to your croft once, then ask it to deploy:

Once it’s deployed, sharing is the same wherever the app came from: invite people, and send them the link.

Roles, permissions and revoking access

Everyone you invite has exactly one role on your croft:

  • Owner runs the account, including billing.
  • Admin helps manage it, including inviting and removing members.
  • Creator builds and ships their own apps, and can share them with others.
  • Member uses the apps that are shared with them.

So most of your team can be Members who open the apps they need and nothing else. You can change someone’s role from the People page at any time. The full breakdown is in roles and permissions.

Someone leaves the team? Remove them once and they’re out of everything, instantly.

Private by default

Croft apps aren’t public. Access is yours to set, app by app, and everything sits behind one sign-on.

Want part of it public - say a survey anyone can fill in, with the results kept private to you? That works too: a public page out front, private results behind your login. But the app itself, and its data, stay with the people you choose.

This is one of the three things that turn an artifact into a real app: a shareable link, a database, and a login.

Next: host it properly

If your app is still stuck in a chat window, the next step is to give it a home. Get your croft, connect your assistant, and share your first app with your team. For more on where to run it, see where to host a vibe-coded app so it stays private.

More from the blog

Start your free trial.

Your team's first app could be live before lunch.