Using Space Build

Pages

Small apps the copilot builds for you: a live dashboard, a form, a button that runs a process. They load instantly with no AI wait.

A page is a small app made for you by the copilot: a view of live data, a form that adds to a table, a button that starts a workflow, a place to upload files. You describe it once. Space builds it, and from then on it simply runs.

The big idea: build once, use forever

	The first time	Every time after
Who works	The AI designs and writes it	Your browser and the server run it
What happens	You describe it and confirm	You open it, and it shows live data
AI calls	As many as building needs	None when you open the page

So pages are fast, cost nothing to open, and never go stale. They always show the current data, each person sees their own view, and one person's data is never carried over to the next.

Building a page

Open Pages and you'll see three areas:

Build a page: describe what you want. This starts a chat.
Suggested for you: ideas for pages based on your own tables and tools, grouped by topic. Pick one to start building it. (Suggestions look only at names, descriptions and column names, never at your actual row values.)
Your pages: the ones you've saved.

Or just ask in any chat. The copilot shows you the page and asks you to confirm before saving.

What a page can do

Ability	Example
Show live data	Rows from a table, or the result of a custom Function
Add or update a row	A “new lead” form
Delete a row	Remove a finished item
Upload a file	Receipts into a folder in your files
Run a workflow	A button that starts a playbook, with its questions shown right under the page
Run a Function	A button that triggers custom logic

Everything a page may change is declared up front and shown on the confirmation card, so you know exactly what it can do before you save. A page can't change anything with no click: changes only happen when a person actually interacts with it.

Workflows on a page

A workflow button shows each run in a panel below the page. It displays only the current question as a friendly form: text, a number, a date, Yes/No choices, a masked box for secrets, or a drop zone for a document. Answer, and it carries on. If it's waiting for a review or for background work, you see progress. When you reopen the page, your recent runs are still there.

Personal pages can be shared read-only with a person or group. The first time they use something that runs code or changes data, they're asked to Allow and load. A page someone else wrote shouldn't act as you without your say-so.
Group and organization pages come from admins and are trusted without that prompt.
Sharing a page never shares its data. Each viewer sees only what they are allowed to see.

A page can be used by someone with no account, such as a customer uploading documents. In the page, choose Share externally.

Setting	What it does
A private link	Long and unguessable. Shown once.
A username and password	Always required, so a forwarded link alone isn't enough. Send the password separately.
Expiry	1 to 90 days, or never (use an expiry for anything sensitive).
Limits	How many submissions and files it accepts.
Fixed values	For example, “this link is for customer C1”. The visitor can't change them.

A visitor can only see the specific columns you chose for their record, and do only what you ticked: add a row, update their own row, upload files, or run an approved workflow (which runs as you, so only tick safe ones). You can revoke a link at any moment, and every use notifies you and is logged.

Pages made by playbooks

A playbook can create a page at the end of a run, such as a results page just for that run, owned by whoever ran it. This gives every run its own tidy view without anyone building it by hand.

Good to know

Pages don't keep a version history yet.
A page reads each data source on every open, so keep them small.
Pages work with tables and Functions. For other systems, put a Function in the middle.