Studio turns your tables into internal apps

Polybase now includes Studio, a no-code builder that lives inside every channel. Pages are composed from blocks — live table views, KPI metric cards, forms, quick-action buttons, task lists and text — then grouped into apps and pinned to the channel's tab bar, right next to Chat and Tasks.

The problem Studio removes is a familiar one: the data already lives in a table, but the tool around it doesn't exist yet. The hiring tracker sits in one grid, the inventory sheet in another, and the interface people actually need is waiting on developer time. With Studio, the team that owns the data assembles the interface itself — no deploys, no separate logins, no new tool to roll out.

Record pages are the centrepiece. Every table row gets its own shareable page: open a row and its editable fields sit next to blocks scoped to that record — this customer's deals, this candidate's interviews, this project's tasks. Context linking filters every block to the record you are looking at, and action buttons can open intake forms pre-filled for it.

Forms close the loop. A grid-based designer controls field widths, widgets, required rules and help text; forms can feed a table as intake, or attach to tasks, meetings and Drive folders so structured data is captured where the work happens. A template gallery ships blueprints — install one and its tables, forms and flows arrive in one click.

Because Studio builds on Tables and Flows, every app inherits the workspace's permissions and its deployment. Teams that self-host Polybase run their internal apps the same way they run everything else — on their own servers, under their own keys.