Project workspace
Project home, activity, members, settings, integrations, migration.
Every project has its own workspace at /p/<id>, with six sub-pages that cover the full project surface area outside the editor itself.
Project home (/p/<id>)
The project's landing page. Three regions:
- Instances — every environment your project ships to (Dev, Staging, UAT, Prod), shown as a table with status pill, URL, who's currently editing in Studio, and a per-instance action menu.
- Bottom card grid — Members on this project, Deploys this month, Project settings shortcut.
- Per-instance actions — open the action menu on any instance row for: Deploy here, Promote to next instance, Deploy history, Rollback.
Instance status badges follow the project lifecycle: idle, deploying, active, error.
Activity (/p/<id>/activity)
Header text: "AI runs, stage transitions, and commits on the bound repo — scoped to project name. Last 50 events."
Two filters at the top: Anyone (filter by who triggered the event) and Type (filter by event category). Export CSV exports the visible rows.
For the full event-type catalogue and the relationship to the workspace-wide feed at /activity, see Activity.
Members (/p/<id>/members)
Two groups:
- Workspace members — everyone in the workspace already has access; listed here for visibility, managed from
/members. - External collaborators — clients, contractors, anyone not in the workspace. Invite by email; they get a sign-up email scoped only to this project.
Roles next to each member are workspace-level: Owner or Admin. The Console / Studio / IIA tier model from Access levels describes how a single Insites identity reaches each platform surface; it isn't a per-row picker on this page.
Settings (/p/<id>/settings)
Sidebar with two sections:
- General — project name and description (shown on the workspace dashboard and in deploy notifications).
- Danger zone — delete the project.
Workspace-wide branding, AI defaults, integrations, and billing live in Workspace settings — they are not project-scoped.
Integrations (/p/<id>/integrations)
Project-scoped integrations. Each card shows a status pill (CONNECTED / not connected / COMING SOON) and an action.
- GitHub (active) — the repo backing the project. Required for deploys. Connects through Insites CloudShell so deploy history and rollback work end-to-end.
- Insites Console (active) — authorise Studio to read instance state and manage deploys against your Insites Console account.
- Slack (coming soon) — notify a channel on deploy, rollback, and member changes.
- Stripe (coming soon) — pull pricing and product data for the project's checkout.
- Figma (coming soon) — import designs from the project's Figma file.
- Webhooks (coming soon) — send raw events to your endpoint.
Migration (/p/<id>/migration)
Always present as a sub-tab. The content depends on whether the project came from the Migrate on-ramp.
For migration projects, displays:
- Source URL (the original site being migrated from).
- Capture date.
- Counts of pages and assets imported.
- Download link for the scrape archive.
Use this page to re-fetch the source archive if the migration needs to be re-run with different settings.
For Build / Connect projects, the page shows:
No migration on file. This project wasn't created via the Migration on-ramp. If you'd like to start a new migration into this project, open the migrate flow from the workspace home.
with a Start a migration → action that deep-links into the Migrate on-ramp.
Workspace members vs external collaborators
Workspace members (/members) automatically have access to every project. External collaborators are invited per-project and only see the projects they're listed on.
Where this lives in code
app/p/[id]/page.tsx— project home.app/p/[id]/activity/page.tsx— activity feed.app/p/[id]/members/page.tsx— project members.app/p/[id]/settings/page.tsx— project settings.app/p/[id]/integrations/page.tsx— integrations.app/p/[id]/migration/page.tsx— migration metadata.