Buyer Start

<aside> 👋

New here? Start with the buyer guide, not the technical foundation. You can get to a working first client portal without understanding the underlying database model.

</aside>

Start here

START HERE — Freelancer Client Portal OS

Setup & use

• First Project Setup
• Your First Project — Walkthrough
• Sharing & Security Guide
• Freelancer OS — Quick Reference
• Client Communication Pack

Technical foundation

<aside> 🧱

This workspace is the product scaffold for the Freelancer Client Portal / Project OS. The database model is intentionally focused on project delivery rather than accounting, marketing, or general business administration.

</aside>

Data model

flowchart LR
    C["Clients"] --> P["Projects"]
    C --> T["Tasks & Requests"]
    C --> F["Feedback & Bugs"]
    C --> D["Deliverables"]
    C --> DE["Decisions"]
    C --> R["Resources & Access"]
    C --> M["Meetings"]
    C --> CR["Change Requests"]
    P --> T
    P --> F
    P --> D
    P --> DE
    P --> R
    P --> M
    P --> CR
    CR --> T
    CR --> DE
    T --> D
    M --> DE

The Client is the commercial root. Projects are the delivery root. Operational records link directly to both where useful so client-level and project-level portals can be built without fragile rollups.

Core design rules

• Client-facing information and internal delivery information share the same source records, but future portal views should expose only client-safe properties.
• Waiting for client is a first-class workflow state, not a note buried inside a task.
• Decisions, deliverables, feedback, and access references are structured records so handover and scope history can be reconstructed later.