Skip to main content

​
Tutorial: Job OS with client portal

Outcome: your team runs jobs on an internal board; AI drafts a brief from intake; invited clients see status and leave feedback without seeing the whole shop. Domain swap: adapt for media production, agencies, shops, or any delivery pipeline. Keep the internal vs client split.

​
Step 1 | Prompt in Build mode

Stay in Build mode and send:
Build a job operating system for a small studio. Roles: producer, client, and owner (owner for settings). Producers create jobs with a client, due date, and stage (intake, in progress, review, delivered). From intake notes, the team can generate an AI brief they can edit. Brief regeneration must be an explicit action, not automatic on every page load. Clients get a portal that shows only their jobs, current stage, and the shared brief summary. Clients can leave feedback. Clients cannot edit stages, see other clients, or open the full producer board. Optional: notify the producer when client feedback is submitted. No public unauthenticated API.

​
Step 2 | Review the plan by journeys

Approve when these journeys look right:
  1. Internal pipeline: producer creates a job, advances stages, and sees the job detail update.
  2. AI brief: producer turns intake notes into an editable brief on demand.
  3. Client portal: client sees only their jobs and status, can leave feedback, and never reaches stage config or other clients.
The client experience must be a distinct surface, not the producer board with filters. Adjust the brief if a journey is missing, then approve.

​
Step 3 | Preview, Access, and invites

Select a project so Preview uses real project data.
  1. Preview as producer: create a job, advance a stage, draft a brief once.
  2. Invite a test client under End-Users with role client (or Preview as client if you already have that role in the project).
  3. Preview as client: only their jobs; no stage editor; no other clients; feedback submits.
  4. Lock the story in App Blueprint → Access, then fix gaps in Build and Preview again.

​
Step 4 | Soft launch

Follow Launch checklist. Add a custom domain later if clients should not see the default portal URL.

​
How to verify (checklist)

  • Preview as producer: pipeline and brief generation work
  • Preview as client: only their jobs; no stage editor; no other clients
  • Client feedback submits and (optional) notifies producer
  • Access matrix matches the staff vs client story