Projects & Teams

Who can open a project, who can issue into it, and who is responsible for it are three different questions in LODE. This module answers all three — then tours project settings, drawing packages for multi-consultant work, and the project list.

10.1 · The model

Access vs assignment

Access is firm-wide. Everyone in your organization can open every project — there is no per-project access grant for internal members. What varies is assignment: an optional responsibility label that says who to contact about a project. Assigning someone does not grant access, and un-assigning them does not remove it.

Assignment gates exactly two things. Issuing — creating or uploading new content into a project — requires an assignment with any role (owners and admins always can). And deleting: issuances and draft content can be deleted by the assigned Project Manager, Principal-in-Charge, or Project Architect; the whole project only by the Project Manager or Principal-in-Charge. Viewing, markup, measuring, comments, and search are never gated.

Roles are picked from one list:

Principal-in-ChargeProject ManagerProject ArchitectArchitectArchitect of RecordInterior DesignerDesignerEngineerConsultantContractorConstruction ManagerClient

One role per person per project; no role at all is the normal state for most members.

What an unassigned member sees

The Issue door on the dashboard greys out with “You’re not assigned to this project, so you can’t issue into it. Ask an organization owner or admin to assign you.” — and if they try anyway, the refusal helpfully names who is assigned, with their roles, so they know who to reach.

10.2 · Team

The Team section

Assignments live in Project Settings › Team (the dashboard’s Team card links straight there with Manage →). The section says it plainly: “Assign responsibilities so teammates know who to contact. Everyone in your firm can already open this project — a role here is a responsibility label, not an access grant.”

Assign. Pick a teammate (“Add a teammate…”), pick a role, click Assign. Changing a role on an existing row saves instantly; the × removes the role — the tooltip reminds you the member keeps access. Only organization owners and admins can manage assignments.

The Project Manager starts at creation. The New Project form has a Project Manager picker — and if you leave it “Unassigned,” the creator becomes the PM, so whoever starts a project can always issue into it. Change the PM afterward in Team like any other role.

Read it back on the dashboard. The Team card lists assigned people only — avatar, name, and “{Role} · {Firm}” — the project’s contact sheet at a glance.

10.3 · Settings

Project settings, on a tour

Project Settings is split into two groups. Project Management is the living project; Project Settings is the record’s machinery. A sticky “Unsaved changes” bar saves the form fields; package, issuance, and AI changes save immediately on their own.

Section	What lives there
Client · Address · Notes	The owner (linked to your firm directory), the site address, and free notes.
Project info	“The program and budget the dashboard reads. All optional.” Program, square footage (with per-building breakouts and a live total), budget, current estimate.
Phases · Packages · Team · External parties	The phase editor (Module 05), delivery-package splits (also Module 05), assignments (§10.2), and outside firms (Module 11).
Details	Name, project number, project type; the Architect / Firm of Record is derived from your organization.
AI on this project	The per-project master switch for clients who require no AI — see DOC — the AI.
Issuances	“Correct issuance names and dates.” Admins can also remove an issuance that was uploaded to the wrong project.
Share Links · Activity	Every link this project has issued, with views, downloads, and revoke (Module 11); the full activity log, exportable as a PDF.
Danger zone	Archive to cold storage, or delete with a 30-day grace — Account & Billing has the distinction.

10.4 · Packages

Drawing packages

A multi-consultant project often runs distinct document scopes — a Building package and an Early Site package, say — each with its own sheet numbering, so Building A101 and Civil A101 never collide. That’s a drawing package, managed in Project Settings › Packages (under the Project Settings group).

The first split names both halves. “Add another package” asks you to name your existing drawings & specs (e.g. Building Package) and the new package (e.g. Early Site Package), each with a color. Until a project has two named packages, no package UI appears anywhere.

Issuances pick their package once. When you open the issuance flow on a multi-package project, one question comes first: “Which package is this issuance for?” — chosen once for the whole session; every sheet inherits it.

The Index gains a Packages filter. Files › Index shows a color-dotted package filter and tags each sheet row; a Sheet order setting chooses between “One package at a time” (each runs start to finish) and “One combined set” (a single discipline order across every package — for a permit or record set).

Two things called packages

Drawing packages organize documents into scopes. Delivery packages (Project Management › Packages) split the project into independently advancing phases — Module 05. A phased site-and-building job may use both.

10.5 · The list

The project list

Projects shows every project as a card — name, sheet / issuance / package counts, a row of discipline color dots, and when it last changed. Search matches project names; tabs filter All · Active · Archived. Archived cards dim with a Cold storage chip (or Restoring while a restore runs).

Reorder turns on drag-and-drop — the order is yours alone, not the firm’s. Each card’s ⋯ menu carries Rename, Archive (or Restore from cold storage), and Delete; archiving always shows the cold-storage warning first, restoring fires immediately.

← Module 09 · Closeout Module 11 · Sharing & Guests →