Guides
Put a Claude artifact behind your company login
Turn a Claude artifact into a private app your team opens with their company Google or Microsoft login. Connect Inhaus, then ask Claude to deploy it.
To put a Claude artifact behind your company login, connect Inhaus to Claude and ask: "Deploy this artifact to Inhaus." Claude sends the artifact's code to Inhaus, which puts it live at its own address where every visitor must sign in with a company Google or Microsoft account.
The artifact becomes a real app: it has its own link, its own list of people who can open it, version history and an access log.
What the company login gives you
An internal tool often shows commissions, customer lists or other private data. A link that opens for anyone who has it is not enough for that. On Inhaus:
- every visitor signs in first, at the Inhaus gateway, before any of the app loads
- you choose who can open it: people, teams or the whole company
- you can remove someone and they are locked out within about 30 seconds
- every open is recorded in the access log
Steps
- Connect Inhaus to Claude
In Claude, go to Settings → Connectors → Add custom connector, name it
Inhausand pastehttps://mcp.inhaus.dev/mcp. Choose Add, then Connect, and approve on inhaus.dev. Full steps: Connect Claude. - Open the chat with your artifact
Turn Inhaus on from the + menu → Connectors in that chat.
- Ask Claude to deploy it
Deploy this artifact to Inhaus as "Listing Checklist".Claude sends the artifact's code as the app's files. Inhaus builds it, bundling React and any npm packages it uses, runs a security scan and puts it live. Claude replies with the link, for example
https://listing-checklist--acme.inhaus.dev. - Open it yourself
Open the link. You see your company's sign-in page, then the app. So far only you have access.
- Share it
Share the listing checklist with ops@acme.com and the operations team, view only.They get an email with the link and sign in with their company account.
What you get once it is an app
- One fixed link. Each update is a new version at the same address.
- Undo. Roll back to any earlier version in seconds. See Versions and rollback.
- Access you control. Add or remove people and teams in the Share dialog, or from the chat.
- A record. Who opened it, shared it or deployed it is in the access log.
Things to know
- The app runs on its own. It no longer runs inside Claude, so features that only exist inside Claude are not available to it.
- API keys belong in secrets. If the artifact calls an outside service with a key, ask Claude to store the key with Inhaus as a secret and read it from server code. The security scan flags keys written into code. See Secrets.
- Outside websites are checked. In a company workspace, every site the app sends data to must be on your admin's allowed list. A new one is flagged and sent to your admin. See Allowed domains.
- Saving data. For uploads such as receipts or photos, the app can use its own private file storage from a small server.
FAQ
Does this work with React artifacts?
Yes. Inhaus bundles TypeScript, JSX and npm packages listed in package.json for the browser, so Claude can send the artifact's code as it is. See Static sites.
What login do people use?
Their company Google or Microsoft account. The app itself never sees a password: the Inhaus gateway checks sign-in and access before any request reaches it.
Can I change the artifact after it is live?
Yes. Ask Claude for the change and to redeploy. It becomes a new version at the same link, and everyone keeps their access. You can roll back if needed.
Can I use my own domain?
Not yet. Apps live at <app>--<workspace>.inhaus.dev.
Can I make it public instead?
Only if your admin allows public links ("anyone with the link"). Use that only for apps with nothing private in them. See General access.