Project Schema

Project title

Project description

Project status

Project start date (YYYY-MM-DD)

Project end date (YYYY-MM-DD)

Project budget as decimal string

Project manager user UUID

Organisational unit (department / team) the project is organisationally located in.

Internal users that make up the project team (independent of orgUnitId). Used for team_member data scope, task filters and notifications.

Associated party UUID

Specific site/address of the associated party

Associated contract UUID

ADR 0274 — STANDALONE billing for this project. When enabled, all billable time of this project (direct PROJECT bookings + its tickets + its tasks) is carved out of the customer collective Leistungsnachweis and billed as its own project LN via POST /projects/:id/generate-performance-record. NEW projects default to enabled=true (materialised at create). EXISTING projects with this object ABSENT are treated as collective (resolveBillingUnit: absent → not standalone) — production-safe, no backfill. `performanceRecord*`/`invoicedAt` back-references are server-set only.

Time budget in minutes

Used time budget in minutes (auto-computed)

Project methodology

Default board UUID

Project tags

Linked sales_order UUID (works for both native and weclapp-sourced orders). Phase 1 of ADR 0139.

Origin of the linked sales-order (ADR 0139)

Aggregated controlling data for the project (ADR 0139). Recomputed by reconcile-order-tasks job and on task/time-record mutations.

weclapp sales order ID

URL to the weclapp sales order detail page

weclapp sales order number (e.g. AB-2026-00042)

weclapp performance record created from the sales order at project billing completion (ADR 0412). Set once — the completion endpoint is idempotent on it.

Number of the weclapp performance record (display/deep-link).

When the weclapp billing completion ran for this project.

weclapp sales invoice created from the performance record (ADR 0412). Set once — the create-invoice endpoint is idempotent on it.

Number of the weclapp sales invoice (display).

URL to the weclapp sales invoice detail page.

When the weclapp sales invoice was created from the billing dialog.

Cached weclapp sales order data

Project cap configuration (budget, hours, deadlines). Used by /projects/:id/limits and warning logic.

Per-project HARD CAP (Obergrenze) as % of the € budget (controlling.totalLoggedAmount / budget). Once logged spend reaches this percent, further time bookings on the project or its tasks are rejected (422 project-cap-exceeded). null/absent ⇒ inherit the tenant default (settings.projects.defaultLimits.budgetCapPercent); 0 ⇒ explicitly no €-cap for this project (overrides a tenant default). Values > 100 allow a controlled overrun. Tolerated missing on existing projects — runtime fallback, no backfill.

Per-project HARD CAP (Obergrenze) as % of the hours budget (usedMinutes / budgetMinutes). Once the projected usage reaches this percent, further time bookings are rejected (422). null/absent ⇒ inherit the tenant default (settings.projects.defaultLimits.hoursCapPercent), else the legacy limits.hardBlockOnExceed flag (= 100%); 0 ⇒ explicitly no hours-cap. Values > 100 allow a controlled overrun. Runtime fallback, no backfill.

Per-project override (%) for the task-progress review lock. When task completion (done/total) first reaches this, the project auto-locks for team-lead review. Null ⇒ use tenant default (settings.projectLock.thresholdPercent, default 70).

Per-project override (%) for the BUDGET-progress review lock (ADR 0191). When budget usage (controlling.totalLoggedAmount / budget €) first reaches this, the project auto-locks for team-lead review — independent of, and OR-combined with, the task-progress lock. Setting a value enables budget-locking for this project even if the tenant default is off. Null ⇒ use tenant default (settings.projectLock.lockOnBudget + budgetThresholdPercent).

Per-project override (%) for the POSITION-PLAN review lock (ADR 0422). When plan usage (controlling.totalLoggedMinutes / totalPlannedMinutes, else the amount equivalent) first reaches this, the project auto-locks for team-lead review — independent of, and OR-combined with, the task and budget locks. Exists because order-materialised projects usually carry no project-level €/hours budget: their planned effort lives in the position limits, so neither of the other two triggers can ever fire there. Setting a value enables plan-locking for this project even if the tenant switch is off. Null ⇒ use tenant default (settings.projectLock.lockOnPlan + planThresholdPercent).

Progress-based review lock state (ADR 0191). One-time checkpoint: once released it does not re-lock at the same threshold. Set/cleared ONLY by the project-lock service and the /projects/:id/review endpoints — listed in protectedFields so generic CRUD PATCH cannot write it.

Customer access configuration for project visibility

task_template this project was instantiated from.

Pinned template version at instantiation time.

Timestamp at which the latest inbound customer email was acknowledged as "handled, no reply needed". Clears the awaiting-reply badge when >= the last inbound email time; a newer inbound email re-arms it. Mirrors opportunity.inboundReplyAckedAt.

User who acknowledged the latest inbound customer email (see inboundReplyAckedAt).