How to share a hiring tracker app with your team

Quick answer

To share a hiring tracker with your team, host it as a private app on Croft and give everyone one URL. Recruiters and hiring managers open it in the browser, work against shared candidate and stage data, and sign in with company login. That is the path for a hiring tracker built with AI for team use, and for turning a hiring spreadsheet to a private app for team workflows: a lasting private app, not an emailed HTML file or a public host.

The tracker works for you. Sharing it is broken.

People 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.

What usually happens:

• You email an HTML export or artifact file. Everyone has a different copy. Stage updates do not sync.
• You drop it on a public host. Candidate names and notes sit on the open web unless you invent login yourself.
• You keep it in a sheet forever. Two people edit at once, and nobody is sure which version is current.
• You demo it once in chat. Later, teammates ask for “that hiring board” and you have to recreate the session.

So the hiring tracker is useful. The team still does not have one live app with one shared board.

If your starting point is a sales pipeline rather than hiring, see How to share an AI-built sales tracker with your team. For stocktake sheets: Replace a spreadsheet stocktake with a private app. For financial models: Turn a spreadsheet financial model into a private team app. For hosting AI-built apps in general: Where to host an app I built with AI. This post is the hiring tracker path.

What sharing a hiring tracker should mean

For a board the hiring team relies on, “share it” is not “any live URL.” It is:

1. A lasting URL teammates can open in a browser
2. Shared saved candidates so every stage update persists for everyone
3. Team sign-in, so outsiders cannot wander into candidate notes
4. Backups and a way to undo a bad change
5. A path to iterate in chat, without babysitting servers

Related reading when you care about recoverability: App hosting with backups and versioning.

Emailed HTML vs public host vs sheet vs Croft

Need	Emailed HTML / artifact	Public AI-app host	Spreadsheet forever	Croft
Team opens their own link	No	Yes	Fragile copies	Yes
Shared candidate data	No	Extra setup	File chaos	Included
Private to your people	File chaos	You build login	File chaos	Built in
Leave one-off demos behind	No	Possible	No	Yes
Keep iterating with AI chat	Limited	Varies	Limited	Yes
No devops required	N/A	Sometimes	N/A	Yes

Croft 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.

Steps: hiring tracker → private team app

1. Get a croft (private server for your workspace).
2. Connect Claude or Cursor over MCP, or use Croft Build in the browser if you prefer not to connect an assistant yet.
3. Hand the assistant the tracker: paste the artifact, export key fields, or describe candidates, stages, and interview notes. Ask it to deploy the hiring tracker as an app on your croft (not to email HTML or publish a public URL).
4. Invite colleagues. They open a normal URL, sign in with company login, and work against the shared hiring board.
5. Keep chatting to change stages, filters, or screens. Deploys and rollbacks stay on the server.

More on the product path: From artifact to app. Prefer Cursor for the next iteration? See host a Cursor app. Ready-made starting points: templates. Need live business data later: connectors.

You 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.

FAQ

How do I share a hiring tracker with my team?

Host it as a private app on Croft, then invite the people who run hiring. They get a normal link and shared candidate data. Details on artifacts to apps and connect Claude.

Can I just email the HTML or artifact?

You 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.

Is this the same as putting the tracker on a public host?

Public hosts are strong for public products. For an internal hiring tracker you usually want a private server and team sign-in by default, not a public URL you lock down after the fact. See also Where to host an app I built with AI.

What if I rebuilt the tracker from a spreadsheet?

Same destination: a private team app. Rebuild the logic as an app (not wrap the sheet forever), deploy to Croft, and invite the people who should update candidates. Related path for sheets: How to turn a Google Sheet into an app.

What if I already built the tracker in Claude or Cursor?

Same steps. Deploy from chat with connect Claude or host a Cursor app, then invite teammates so they can sign in and use the shared hiring board.

Do I need to be technical?

No. 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.

How much does Croft cost?

Solo from $24/month on annual billing, Team $99/month on annual. 7-day free trial, no card to start. See pricing.

Get your croft →  ·  Artifacts to apps →  ·  Connect Claude →

More from the blog