The project, the tasks and the team. Connected.
Build a project app with related tasks and clients, so every view draws from the same work and respects the same access rules.
Give the work a relational home
Start with connected tables. A shared name in two spreadsheets is not a relationship.


Projects
Record client, lead and timeline in one place.
Tasks
Link each task to a project and an assignee.
Clients
Keep client details separate from the projects they commission.
Decide who sees what, before the first screen
User roles grant access per table, row, field and action. Every surface follows those rules.
Sam's rule
Project members
Scope access to assigned projects and their related tasks.
Clients
Grant visibility to their own project records and permitted fields.
Project leads
Decide who may change assignments and project deadlines.
Different jobs deserve different screens
The Data grid is the starting point. Interface ideas can be described to the assistant and built over the same authorized data.


My tasks
A Data view filtered to assigned work and grouped by project.
Project dashboard
An interface summarizing deadlines and task stages.
Client progress
A client-facing page built on the client's authorized rows.
Try this as your app brief
"Build a project app with Clients, Projects and Tasks. Team members see assigned projects. Clients see only their projects, with internal planning notes excluded."
This is an app design example, not a ready-made template. Explore the product or other use cases.
Keep exploring


Get access to Grid82
Start from this design, or from your own. Access opens from the waitlist.