Publish & share your app

Publishing turns your draft into the app your team actually uses — a validated, versioned snapshot at its own address. Your edits stay private until the next publish.

What publish does

• Validates everything first.Broken references, unusable layouts, missing role setup — blocking issues are listed with links to the exact spot, and the app publishes only when they're fixed.
• Snapshots the draft as an immutable version (with optional release notes), so the live app never changes under your feet mid-edit.
• Goes live instantly. The published app serves at /a/<your-app>; open sessions pick up the new version in place.

Version history and rolling back

Every publish and every save point is kept under Settings → Versions. Preview opens any older version in the real app so you can look around before deciding; Restorecopies that version into your draft as a new save point (“Restored from Version 3”) — nothing in the history is overwritten, and your users keep seeing the current published app until you publish the restored draft. Older entries are removed automatically after a plan-dependent window (shown at the top of the list); the versions your users currently run — Default and Latest — are always kept.

Who can use it

App access follows your roles: each user gets a role, and roles decide tables, rows, and views. You can even drive the user list from one of your own tables — see Users. Published apps also install as a PWA with your app's icon and name.

Sharing outside the team

Need to show a view to someone without an account? Create a public link — a read-only page or an anonymous submission form served at an unguessable address you can revoke at any time.