Configure the technical office: stages, types, teams and survey settings

A stage is four fields: Stage Name, Sequence (the kanban order), Folded in Kanban and Active. The Folded flag does far more than collapse a column — it is what the system treats as "closed": folded-stage requests are excluded from the overdue calculation, shown muted in lists, and a folded technical-request stage is also what makes the surveyor portal refuse further re-visit requests on that job. Two behaviours to keep in mind:

A type carries a Type Name, a one-line Description, an Active flag and a rich-text Note. The description and note are not decoration: the request dialog shows them to whoever raises a request of this type, and copies them onto the request itself — the note is your standing instruction sheet per kind of work.

The two survey fields wire types into the measuring flow. With Auto Create Survey on and a Survey Type chosen (Pre-Quote Survey or Production Survey), every request created with this type — and every existing request switched to it — gets a draft survey of that type created automatically, assigned to whoever created the request, unless a live survey of that type already exists on it. The Survey Type becomes required as soon as the toggle is on; a half-configured type is refused with "Please select a Survey Type for request type '…': 'Auto Create Survey' has no effect without one."

Tags are a name, a colour and an Active flag; Urgent, Installation, Repair, Maintenance and Consultation ship as starters. Teams are a Team Name, a Team Leader and a member list of employees (Installation Team, Fabrication Team and Technical Support ship ready). Both are labels for grouping and filtering: assigning a team to a request routes nothing and notifies nobody — the request's Manager field is the assignment that matters.

One settings row exists per company (creating a second raises "Configuration already exists for this company!"). What each field really does:

A template is a named bundle of defaults: which survey type it applies to, default Site Conditions and Access notes, and template items that pair a Location Pattern with default window position, drainage face, aperture finish, threshold and scaffolding values. In this release the library is exactly that — a library: the only action wired to it is Clone Template (in the Actions menu of a template), which copies a template with or without its lines. No button on a survey applies a template automatically, so treat templates as documented standards your surveyors read, not as an automation.

Each rule names a Trigger Event, an Apply To scope (all surveys, pre-quote only, production only), the channels, and the recipients. Events that actually fire are the workflow ones — Survey Created, Survey Assigned to Surveyor, Survey Started, Survey Completed, Survey Pending Approval, Survey Approved and Survey Rejected (a rejection is the move from pending approval back to draft). They fire on the real transition however it happens — form buttons, bulk actions, or the surveyor portal.

Renamed stages came back after an update — the five shipped stages are updatable seed records; the upgrade restored their names. Create your own stages for custom names.

A request type saved from the form but the list refuses the same change — both views enforce the same rule: Auto Create Survey without a Survey Type is always refused.

A notification rule stays silent — check, in order: the rule is Active; its Apply To matches the survey's type; the channel has a template (email rules without an email template send nothing); and the event is one of the workflow events. The Scheduled Survey Reminder and Survey Overdue events have no scheduler behind them in this release and never fire.

"Configuration already exists for this company!" — someone pressed New on the Settings screen; open and edit the existing row instead.