{"slug": "how-to-share-a-hiring-tracker-app-with-your-team", "title": "How to share a hiring tracker app with your team", "summary": "Croft published a guide on September 30, 2026 describing how teams can host an AI-built hiring tracker as a private app on its platform, giving recruiters and hiring managers one URL with shared candidate and stage data, company sign-in, and backups instead of emailed HTML exports or public hosting. The post, written by Rich Chetwynd, outlines a four-step setup: create a croft private server, connect Claude or Cursor over MCP or use Croft Build in the browser, hand the assistant the tracker's candidates, stages and interview notes, then deploy it as an app on the croft.", "body_md": "[Blog](https://oncroft.net/blog/) · September 30, 2026 · Rich Chetwynd\n\n# How to share a hiring tracker app with your team\n\nHost a hiring tracker built with AI as a private team app on Croft. One URL, shared candidate data, company login, backups. Not emailed HTML or a public host.\n\n## Quick answer\n\nTo **share a hiring tracker with your team**, host it as a private app on Croft\nand give everyone one URL. Recruiters and hiring managers open it in the\nbrowser, work against **shared candidate and stage data**, and sign in with\ncompany login. That is the path for a **hiring tracker built with AI for team**\nuse, and for turning a **hiring spreadsheet to a private app for team**\nworkflows: a lasting private app, not an emailed HTML file or a public host.\n\n## The tracker works for you. Sharing it is broken.\n\nPeople already build hiring trackers with Claude, Cursor, or a rebuilt sheet: candidates, stages, interview notes, next steps. The app often works fine for the person who built it. The cliff is handing it to the rest of the hiring team.\n\nWhat usually happens:\n\n- You email an HTML export or artifact file. Everyone has a different copy. Stage updates do not sync.\n- You drop it on a public host. Candidate names and notes sit on the open web unless you invent login yourself.\n- You keep it in a sheet forever. Two people edit at once, and nobody is sure which version is current.\n- You demo it once in chat. Later, teammates ask for “that hiring board” and you have to recreate the session.\n\nSo the hiring tracker is useful. The team still does not have one live app with one shared board.\n\nIf your starting point is a sales pipeline rather than hiring, see\n[How to share an AI-built sales tracker with your team](https://oncroft.net/blog/sales-tracker-ai-app-for-your-team/).\nFor stocktake sheets:\n[Replace a spreadsheet stocktake with a private app](https://oncroft.net/blog/spreadsheet-stocktake-to-private-app/).\nFor financial models:\n[Turn a spreadsheet financial model into a private team app](https://oncroft.net/blog/spreadsheet-financial-model-to-private-app/).\nFor hosting AI-built apps in general:\n[Where to host an app I built with AI](https://oncroft.net/blog/where-to-host-an-app-i-built-with-ai/).\nThis post is the hiring tracker path.\n\n## What sharing a hiring tracker should mean\n\nFor a board the hiring team relies on, “share it” is not “any live URL.” It is:\n\n1. A **lasting URL** teammates can open in a browser\n2. **Shared saved candidates** so every stage update persists for everyone\n3. **Team sign-in** , so outsiders cannot wander into candidate notes\n4. **Backups and a way to undo** a bad change\n5. A path to **iterate in chat** , without babysitting servers\n\nRelated reading when you care about recoverability:\n[App hosting with backups and versioning](https://oncroft.net/blog/app-hosting-with-backups-and-versioning/).\n\n## Emailed HTML vs public host vs sheet vs Croft\n\n| Need | Emailed HTML / artifact | Public AI-app host | Spreadsheet forever | Croft | \n|---|---|---|---|---|\n| Team opens their own link | No | Yes | Fragile copies | Yes | \n| Shared candidate data | No | Extra setup | File chaos | Included | \n| Private to your people | File chaos | You build login | File chaos | Built in | \n| Leave one-off demos behind | No | Possible | No | Yes | \n| Keep iterating with AI chat | Limited | Varies | Limited | Yes | \n| No devops required | N/A | Sometimes | N/A | Yes | \n\nCroft is the private place for vibe-coded and AI-artifact apps. It is not a public AI-SaaS host, and it is not “keep the sheet forever and wrap it.” You bring the hiring tracker; Croft gives your team a shared app on a private server.\n\n## Steps: hiring tracker → private team app\n\n1. Get a croft (private server for your workspace).\n2. [Connect Claude](https://oncroft.net/connect/claude/) or[Cursor](https://oncroft.net/connect/cursor/) over MCP, or\nuse[Croft Build](https://oncroft.net/build/) in the browser if you prefer not to connect an\nassistant yet.\n3. Hand the assistant the tracker: paste the artifact, export key fields, or\ndescribe candidates, stages, and interview notes. Ask it to **deploy the\nhiring tracker as an app on your croft** (not to email HTML or publish a\npublic URL).\n4. Invite colleagues. They open a normal URL, sign in with company login, and work against the shared hiring board.\n5. Keep chatting to change stages, filters, or screens. Deploys and rollbacks stay on the server.\n\nMore on the product path: [From artifact to app](https://oncroft.net/artifacts/). Prefer Cursor for\nthe next iteration? See [host a Cursor app](https://oncroft.net/host-cursor-app/). Ready-made\nstarting points: [templates](https://oncroft.net/templates/). Need live business data later:\n[connectors](https://oncroft.net/connectors/).\n\nYou still do not need to learn nginx, Docker, or “how to deploy.” The point of Croft is that the assistant can ship the app for you.\n\n## FAQ\n\n### How do I share a hiring tracker with my team?\n\nHost it as a private app on Croft, then invite the people who run hiring. They\nget a normal link and shared candidate data. Details on\n[artifacts to apps](https://oncroft.net/artifacts/) and [connect Claude](https://oncroft.net/connect/claude/).\n\n### Can I just email the HTML or artifact?\n\nYou can, once. Then someone moves a candidate to “interview,” another person has an old copy, and nobody has one source of truth. That is fine for a demo. It is not fine for a tracker the hiring team uses every day.\n\n### Is this the same as putting the tracker on a public host?\n\nPublic hosts are strong for public products. For an internal hiring tracker you\nusually want a private server and team sign-in by default, not a public URL you\nlock down after the fact. See also\n[Where to host an app I built with AI](https://oncroft.net/blog/where-to-host-an-app-i-built-with-ai/).\n\n### What if I rebuilt the tracker from a spreadsheet?\n\nSame destination: a private team app. Rebuild the logic as an app (not wrap the\nsheet forever), deploy to Croft, and invite the people who should update\ncandidates. Related path for sheets:\n[How to turn a Google Sheet into an app](https://oncroft.net/blog/how-to-turn-a-google-sheet-into-an-app/).\n\n### What if I already built the tracker in Claude or Cursor?\n\nSame steps. Deploy from chat with [connect Claude](https://oncroft.net/connect/claude/) or\n[host a Cursor app](https://oncroft.net/host-cursor-app/), then invite teammates so they can sign\nin and use the shared hiring board.\n\n### Do I need to be technical?\n\nNo. If you can maintain a hiring sheet or describe your stages to an assistant, you can ask it to deploy to Croft. The people who get the most from this are ops and hiring experts, not platform engineers.\n\n### How much does Croft cost?\n\nSolo from $24/month on annual billing, Team $99/month on annual. 7-day free\ntrial, no card to start. See [pricing](https://oncroft.net/pricing/).\n\n## Stake out your croft.\n\nYour team's first app could be live before lunch.\n\n[Get your croft](https://app.oncroft.net/signup)\n\n7 days free, no card to start. From $24/month - cancel anytime and take everything with you.", "url": "https://wpnews.pro/news/how-to-share-a-hiring-tracker-app-with-your-team", "canonical_source": "https://oncroft.net/blog/hiring-tracker-app-for-your-team/", "published_at": "2026-09-29 11:00:00+00:00", "updated_at": "2026-09-29 19:21:41.428675+00:00", "lang": "en", "topics": ["ai-tools", "agent-protocols", "ai-products"], "entities": ["Croft", "Rich Chetwynd", "Claude", "Cursor", "Croft Build", "MCP"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/how-to-share-a-hiring-tracker-app-with-your-team", "markdown": "https://wpnews.pro/news/how-to-share-a-hiring-tracker-app-with-your-team.md", "text": "https://wpnews.pro/news/how-to-share-a-hiring-tracker-app-with-your-team.txt", "jsonld": "https://wpnews.pro/news/how-to-share-a-hiring-tracker-app-with-your-team.jsonld"}}