Let colleagues in with the sign-in they already use
Your colleagues don't need a new account or a new password to open an app you built. They sign in with something they already have: a link sent to their email, a passkey on their phone or laptop, or, on paid plans, their Google or Microsoft account. A new app is private, so only you and the people you add can open it. Ask Claude to add people by email, to open the app to your whole workspace or, on paid plans, to everyone at your company's email domain or to the public.
Three ways your colleagues can sign in
An emailed link, on every plan. Your colleague opens the app's address, types their email and gets a message with a link. It works once and expires after 15 minutes. No Haechy account, no password to remember or reset.
A passkey, on every plan. After the first emailed link, the browser offers to add a passkey, which means signing in next time with Face ID, a fingerprint or the device PIN. "Not now" is remembered in that browser, so nobody is nagged. One person can keep up to 20 passkeys. A passkey only proves who they are. Whether they are allowed into the app is still decided by the app's access rule, so removing someone from the list shuts the door at their next sign-in, whatever they have saved.
Google or Microsoft, on Pro, Team and Business. Colleagues choose "Sign in with Google" or "Sign in with Microsoft" and use the work account they already have open all day. Haechy accepts accounts with a verified email. This is built and is being switched on for paid plans. It isn't on Free.
All three work on your own web address too, if you use one on a paid plan.
Four ways to open an app
| Who gets in | Plans | |
|---|---|---|
Private (private, the default) | You, the workspace admins, and the people you list for that app | All |
Workspace (team) | Everyone in your workspace, plus anyone you list | All |
Company domain (domain) | Anyone with an email address at the domains you name (up to 20) | Paid |
Public (public) | Anyone, with no sign-in | Paid |
Domain mode can't use public email providers such as gmail.com or outlook.com, since that would let in anyone with a free account. The workspace owner and admins can always open every app.
Set the mode by asking Claude ("make it open to everyone at northwind.example"). The tool behind it is set_app_access.
Before an app goes public, you see what the public could open
Public mode (paid plans) lets anyone on the internet open the app with no sign-in, on every page. So Haechy doesn't switch it on from a request alone. Before it goes public, Haechy shows you the pages and endpoints anyone could open without signing in, next to the outside services the app is approved to call. If it can't list them all (an address that answers anything under it, for example), it says so. The app goes public only after you confirm in the console. Claude can't confirm for you.
It is a list of what the app answers, so read it as you would read a menu before opening the doors. If a page shows colleagues' names, numbers or money, don't confirm; keep the app on one of the sign-in modes.
Other ways in without signing in
Public mode is the only setting that opens the app's code to people who haven't signed in. The other ways a request can arrive without a sign-in were checked one by one. None of them lets someone who hasn't signed in reach the app's code:
- Scheduled jobs and the check after going live. Only Haechy's own server starts them. Requests from the internet can't fake them.
- File links. An app can hand out a signed link to one stored file. The link works for 5 minutes by default and 1 hour at most, and only the app can create one. Whoever holds the link can use it until it expires, so share it like a document you are emailing.
- Webhooks from outside services. A private app can't receive them, because there is no per-path exception to sign-in.
How many people can sign in on your plan
The number counts distinct email addresses across your whole workspace, builders included.
| Free | Pro | Team | Business | |
|---|---|---|---|---|
| People who can sign in | 5 | 25 | 125 | 500 (more: talk to us) |
| Emailed link and passkeys | Yes | Yes | Yes | Yes |
| Google and Microsoft | No | Yes | Yes | Yes |
| Open to everyone at your company's email domain, or to the public | No | Yes | Yes | Yes |
Numbers as of November 2026. The full list of limits is in plan limits.
Adding and removing people
- You
Let Sam and Priya use the expense tracker.
- Tool
add_app_membersexpense-trackerDoneAdded 2 members to expense-tracker. Share the app's address with them.
- Claude
Done. Send Sam and Priya the address expense-tracker.haechy.app. When they open it, Haechy emails them a sign-in link.
Claude uses add_app_members and remove_app_members, and list_app_members shows who is on the list. Adding someone doesn't send them an email: share the address, and Haechy sends the sign-in link when they open it. Removing someone ends their access at their next sign-in, which can be up to 12 hours later, because a session that has already started runs its course. If it can't wait, ask Claude to stop the app (stop_app) until then; code, data and settings are kept.
What your colleague sees
They open the app's address and are asked for their email. They receive a message titled "Sign in to <app name>", which says the app is hosted on Haechy for you. The link works once and expires after 15 minutes. After that the browser stays signed in for 12 hours, and the same link covers your other apps in the workspace for that time. There is no password to remember or reset. If they add a passkey, the next sign-in is one touch or one look.
On Pro, Team and Business they can choose Google or Microsoft instead of the emailed link. On Free the link and passkeys are the options, so tell Free-plan colleagues to expect an email.
What if someone who isn't on the list tries?
A person who isn't allowed in sees an access-denied page. You get one email per person per day saying that "<email> asked for access to <app>", so you can add them if that was expected. If the reason is the plan's people limit, the email says so.
Teammates and app members are different
An app member can open one app. A teammate belongs to the workspace itself, and is added with invite_teammates, which sends them an invitation. Teammates have a role: member, or admin. Admins can open every app and can also approve outside services for apps, which is why you should give the role to few people (how approvals work).
Sign-in is one of several things an app can do once it is online. See what else your app can do.
The people limit
The plan counts distinct email addresses across workspace members and the app members of apps that haven't been deleted, so one person on three apps counts once. Visitors who get in through company-domain or public mode are not counted. On Free that is 5 people, you included; the sixth is refused with a link to upgrade, and apps that are already running carry on. The numbers for every plan are in plan limits and on pricing.
Not sure whether to share a Claude artifact instead? What is the safest way to share an app you built with Claude? sets the two side by side.