# How to share a shift roster app with your team > Source: > Published: 2026-10-01 11:00:00+00:00 [Blog](https://oncroft.net/blog/) · October 2, 2026 · Rich Chetwynd # How to share a shift roster app with your team Host a shift roster built with AI as a private team app on Croft. One URL, shared shifts, company login, backups. Not emailed HTML or a public host. ## Quick answer To **share a shift roster with your team**, host it as a private app on Croft and give everyone one URL. Managers and staff open it in the browser, work against **shared shifts and coverage**, and sign in with company login. That is the path for a **shift planner built with AI for team** use, and for turning a **spreadsheet roster to a private app for team** workflows: a lasting private app, not an emailed HTML file or a public host. ## The roster works for you. Sharing it is broken. People already build shift rosters with Claude, Cursor, or a rebuilt sheet: who works when, coverage gaps, swap requests, next week. The app often works fine for the person who built it. The cliff is handing it to the rest of the team. What usually happens: - You email an HTML export or artifact file. Everyone has a different copy. Shift swaps do not sync. - You drop it on a public host. Names and hours 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 roster” and you have to recreate the session. So the shift roster is useful. The team still does not have one live app with one shared schedule. If your starting point is a hiring board rather than a roster, see [How to share a hiring tracker app with your team](https://oncroft.net/blog/hiring-tracker-app-for-your-team/). For sales pipelines: [How to share an AI-built sales tracker with your team](https://oncroft.net/blog/sales-tracker-ai-app-for-your-team/). For stocktake sheets: [Replace a spreadsheet stocktake with a private app](https://oncroft.net/blog/spreadsheet-stocktake-to-private-app/). For financial models: [Turn a spreadsheet financial model into a private team app](https://oncroft.net/blog/spreadsheet-financial-model-to-private-app/). For hosting AI-built apps in general: [Where to host an app I built with AI](https://oncroft.net/blog/where-to-host-an-app-i-built-with-ai/). This post is the shift roster path. ## What sharing a shift roster should mean For a schedule the 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 shifts** so every swap and coverage update persists for everyone 3. **Team sign-in** , so outsiders cannot wander into names and hours 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](https://oncroft.net/blog/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 shift 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 shift roster; Croft gives your team a shared app on a private server. ## Steps: shift roster → private team app 1. Get a croft (private server for your workspace). 2. [Connect Claude](https://oncroft.net/connect/claude/) or[Cursor](https://oncroft.net/connect/cursor/) over MCP, or use[Croft Build](https://oncroft.net/build/) in the browser if you prefer not to connect an assistant yet. 3. Hand the assistant the roster: paste the artifact, export key fields, or describe roles, shifts, and coverage rules. Ask it to **deploy the shift roster 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 roster. 5. Keep chatting to change views, swap flows, or screens. Deploys and rollbacks stay on the server. More on the product path: [From artifact to app](https://oncroft.net/artifacts/). Prefer Cursor for the next iteration? See [host a Cursor app](https://oncroft.net/host-cursor-app/). Ready-made starting points: [templates](https://oncroft.net/templates/). Need live business data later: [connectors](https://oncroft.net/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 shift roster with my team? Host it as a private app on Croft, then invite the people who run and work the shifts. They get a normal link and shared roster data. Details on [artifacts to apps](https://oncroft.net/artifacts/) and [connect Claude](https://oncroft.net/connect/claude/). ### Can I just email the HTML or artifact? You can, once. Then someone swaps a shift, 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 roster the team uses every week. ### Is this the same as putting the roster on a public host? Public hosts are strong for public products. For an internal shift roster 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](https://oncroft.net/blog/where-to-host-an-app-i-built-with-ai/). ### What if I rebuilt the roster 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 shifts. Related path for sheets: [How to turn a Google Sheet into an app](https://oncroft.net/blog/how-to-turn-a-google-sheet-into-an-app/). ### What if I already built the roster in Claude or Cursor? Same steps. Deploy from chat with [connect Claude](https://oncroft.net/connect/claude/) or [host a Cursor app](https://oncroft.net/host-cursor-app/), then invite teammates so they can sign in and use the shared roster. ### Do I need to be technical? No. If you can maintain a roster sheet or describe your shifts to an assistant, you can ask it to deploy to Croft. The people who get the most from this are ops and floor 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](https://oncroft.net/pricing/). ## Stake out your croft. Your team's first app could be live before lunch. [Get your croft](https://app.oncroft.net/signup) 7 days free, no card to start. From $24/month - cancel anytime and take everything with you.