> ## Documentation Index
> Fetch the complete documentation index at: https://docs.genieforge.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Tutorial: Assigned work portal

> Build a two-sided app where staff assign plans, participants run today's work, and proof uploads come back for review.

# Tutorial: Assigned work portal

Outcome: staff assign structured work; participants see only their plan, log progress, and upload proof; staff review on a separate surface. Same shape as coaching, mentoring, or supervised field work. Swap the domain language for yours.

## What you will assemble

| Piece     | Role in the app                                                 |
| --------- | --------------------------------------------------------------- |
| Roles     | `staff`, `participant`                                          |
| Data      | Participants, work blocks, sessions, proof uploads              |
| Forms     | Intake; build / edit work block; cancel session                 |
| Pages     | Staff dashboard; participant "today"; library; review workspace |
| Tools     | Assign block, log progress, save proof, complete / cancel       |
| Agents    | Optional staff agent (assign only) and participant agent (log)  |
| End users | Invite participants into the project portal                     |

## Step 1 | Prompt in Build mode

> Build an assigned work portal. Staff invite participants, collect a short intake, and assign categorized work blocks from a reusable library. Participants open a Today page with their current block, log progress, and upload proof (photo or short video). Staff have a review workspace to see proof and adjust the next block. Participants never see other participants' plans. Roles: staff, participant.

Approve when staff and participant pages are separate and role-gated.

## Step 2 | Assignment path

**Library → create work block tool → assign to participant → participant Today page updates**

**Preview as** staff to assign, then **Preview as** participant to confirm only their block appears.

## Step 3 | Proof and review

Wire upload to project files (or the pattern Build proposes), then a staff page that lists pending reviews. Completing a session should clear Today and show history for that participant only.

## Step 4 | Access review

Open **App Blueprint → Access** for `participant`. They must not edit the library, reassign others, or open staff dashboards. Re-check with [Preview as](/users-and-access/preview-as).

## Step 5 | Invite and launch

Invite real participants under **End-Users**. Confirm the portal lands on Today, not Build mode. Then follow [Launch checklist](/getting-started/launch-checklist).

## Related

* [Inviting end users](/users-and-access/inviting-end-users)
* [Roles and access control](/users-and-access/roles-and-access-control)
* [Portal](/projects-and-domains/portal)
* [App files vs project files](/managing-data/app-files-vs-project-files)