The team edition versus the personal edition
The same tables, formulas, views and dashboards, running two ways — the personal edition on your own computer, the team edition hosted with accounts, permissions and several people at once. Which to pick, and how data moves between them.
Note
The team edition is a hosted service operated for the Chinese market, at www.tabledi.com.cn, and its console and support are in Chinese. What this site sells is the desktop app, which is single-user by design — it makes no promise of sharing or multi-device sync. This chapter is here so you know what the difference is, and for anyone who does use both.
Side by side
| Personal (desktop) | Team (hosted) | |
|---|---|---|
| Runs where | Your computer, works offline | Hosted, used in a browser |
| Account | None; nothing to sign into | Email registration and sign-in |
| Data | A folder on this machine | Hosted (the enterprise tier can be privately deployed with its own object storage) |
| People | One | Several, editing at once, with workspaces and projects |
| Permissions | None | Admin / editor / viewer / user, down to a table or a project |
| Sharing dashboards, public forms | Not available — no outward-facing server | Public links, invite links, QR codes |
| Data connections, automation, API | Yes; the engine runs only while the app is open | Yes; runs around the clock in the cloud |
| AI | Your own API key | Provided by the platform, metered by plan |
| Paying | Free tier plus monthly / yearly / lifetime | Annual subscription, in CNY |
| In this manual | Every earlier chapter | This chapter |
The table editor, the formula panels, views and dashboards behave identically on both — everything earlier in this manual holds for the team edition too.
Which one
- One person building tables, reconciling, producing reports: the personal edition. The data is private, there is no latency, and nothing waits on an upload.
- Several people editing one table at once, different permissions for different people, a dashboard the whole company watches: the team edition.
- Personal first, team later: data moves across as a
.tdbk(ask us for help), or table by table as exported templates added on the other side. - Coming the other way, from the hosted service to the desktop app: Moving from the cloud edition.