Giving colleagues access to an app without making them create accounts
"No accounts" can mean three different things, and each has a different answer. A one-time link sent to the colleague's work email means no password and no new account, and it suits most team tools. Using the work email people already have is the neater fit when your IT team is involved. An open link with no sign-in at all is right only for information you would be happy to put on a poster.
Updated 7 November 2026.
What people usually mean
Sometimes it is "no new password to remember". Sometimes it is "nobody should need a Claude or ChatGPT account just to open my tool". Sometimes it really is "no sign-in, just a link". Decide which one you want first, because the third is the riskiest and the first two can be done with a sign-in that feels like none.
A one-time emailed link
The colleague opens the app's address and types their email. They get a message with a link that works once and expires after 15 minutes. Opening it shows a confirm button (mail scanners often open links before a person does, and the button keeps the scanner from using it up), and then the person is in. Their browser stays signed in for 12 hours.
This is how Haechy does it for everyone you add to an app. Nobody creates a Haechy account, picks a password, or needs a Claude account. You add people by asking Claude to add their emails; adding someone doesn't send them anything, so share the app's address and the link goes out when they open it. Someone who isn't on the list sees an access-denied page, and you get one email per person per day saying who asked.
What can go wrong: a link in someone's inbox is only as safe as that inbox. And because the session lasts 12 hours, removing a person takes effect at their next sign-in, up to 12 hours later. If you can't wait, stop the app.
Cloudflare Access works on the same idea. Its one-time PIN is sent to approved email addresses, expires after 10 minutes and is single-use. The difference is setup: the app has to sit on a domain behind Cloudflare, and someone has to write the access policy. Its free tier covers teams under 50 users (per Cloudflare's pages, checked 7 November 2026). If your company has an IT person, this is an established route and a good one.
The work email people already have
Haechy has a company-domain mode on paid plans. Anyone with an address at the domains you name, up to 20, can open the app after the same emailed link. Free email providers such as gmail.com or outlook.com are refused in this mode. People who get in this way aren't counted against your plan's people limit. It saves you from adding each person by hand and it means a new hire can open the tool on day one. It also means anyone who can receive mail at that domain can get in, so it suits a tool the whole company may see.
If your company needs people to use the single login it already has for everything else, Haechy doesn't plug into that today. Cloudflare Access can, and so can sign-in with Google through a service such as Supabase Auth, where colleagues use a Google account they already have and the builder sets up the connection. That is more work, and it is the right choice when IT insists on one login system.
Tailscale takes a different route: colleagues join a private network after signing in through your identity provider, and the app is only reachable from inside it. Its personal plan is free for up to 6 users and is for non-commercial use; the standard plan is $8 per user a month (per Tailscale's pricing page, checked 7 November 2026). Each person installs Tailscale on their device.
An open link
Haechy's public mode, on paid plans, lets anyone with the address open the app with no sign-in. There is no audit trail of who looked, and the link can be forwarded to anyone. Use it for something you would print and pin to a wall. For anything that holds colleagues' names, numbers or money, use one of the two options above. Before an app goes public, Haechy lists the pages and endpoints anyone could then open without signing in, and it goes public only after you confirm.
Haechy's four access modes
| Mode | Who gets in | Plans |
|---|---|---|
| Private (default) | You, workspace admins and people you list for that app | All, including Free |
| Workspace | Everyone in your workspace plus anyone you list | All |
| Company domain | Anyone with an email at up to 20 domains you name | Paid |
| Public | Anyone, no sign-in | Paid |
On the Free plan, up to 5 people can sign in across all your apps, counting you, and the sixth is refused with a link to upgrade. Apps already running carry on. Paid plans allow 25, 125 and 500 people; see the pricing page (checkout isn't open yet). Colleagues who use your apps need no plan of their own.
When someone leaves
Remove their email from the app. It takes effect at their next sign-in, which can be up to 12 hours away because the session lasts that long. If that is too slow, stop the app until the time has passed.
More
The full sign-in details are in Sharing and sign-in. If you are comparing places to host the app, see hosting an internal tool with a database and logins. How Claude's own sharing handles this is in the guide to sharing a Claude-built app, and your IT team will find the controls on the IT page and the security page.