StoryOS

Templates · Agency

Client Space

A per-client space you share with the client — tasks, deliverables, meetings, requests.

Without it

The client asks for status on Slack, approvals happen in email, and neither of you can say what was agreed three weeks ago.

A StoryOS board view, the kind Client Space installs

A real board view in StoryOS — the shape Client Space installs.

What gets installed

4 connected databases, with fields, relations and views pre-wired.

Tasks

State · selectPriority · selectLabels · multi_selectAssignee · userDue Date · dateClient Approval · select

Deliverables

Status · selectType · selectDue Date · dateLink · urlVersion · number

Meetings

Date · dateType · selectAttendees · userRecording · url

Requests

Status · selectRequested By · textRequested On · date

Ships with 7 saved views: Shared Board (board) · Waiting on Client (table) · Needs Approval (table) · Delivery Board (board) · Upcoming (table) · Meeting Calendar (calendar) · Request Board (board)

How this template works

How this works

This is the space you SHARE with a client (invite them as a guest with editor access — they work, they just can't touch structure). Tasks with a Client Approval state, Deliverables, Meetings and Requests for their asks.

The loop

  • Client requests come into Requests; you convert accepted ones into Tasks.
  • Deliverables move to Client Approval; the client flips them from their side.
  • Meeting notes live in Meetings — shared memory beats email threads.

Then put an agent on it

An agent drafts the "ready for your review" note when a deliverable moves to review, so the client hears from you before they have to ask.

It runs on your own Claude or ChatGPT over MCP — never metered, never marked up — and every move it makes waits at an approval gate. How agent runs work →

Install Client Space in one click.

Start free — 30 days of Pro, no card. Unlimited records, and your own AI is never metered.

Template contents synced from the product registry, 2026-07-26.