Config Studio
Config Studio holds the design rules of every area landplan.io designs in: Default, each state and each county. The daily flow, the loading rates, the systems an area allows, the fields and limits of each system's cross section, the setbacks, the approved products and the prices all come from it. It is in Admin › Config Studio, and only admins can open it.
Video coming soon: Config Studio (admins). Until then, follow the steps on this page.
Designers never open Config Studio. They see its values as the starting values, limits and checks of their designs.
Open Config Studio
- Open Admin (
landplan.io/admin), signed in as an admin. - Click Config Studio in the left menu. Its own address is
landplan.io/admin/config-studio.
The bar at the top has:
| Control | What it does |
|---|---|
| Editing | Area rules edits an area's design rules. Organization defaults edits an organization's own starting values and prices over the area's. |
| Show values in | US or Metric. Values are stored in US units either way. |
| In the app | Released or Preview. With Preview, the map uses the areas kept for admins and the values waiting for review, for you only. Reload the map after you switch. |
| The bell | Needs attention: values waiting check, catalog conflicts, changed regulation sources, broken links and areas not reviewed in 12 months. |
The tabs under the bar are Areas, Materials, Review queue, Runs, Catalog conflicts and Coverage.
What the counts mean:
- Values waiting check: values proposed by Claude runs and the audit that no one has approved or rejected yet in the Review queue. They change nothing until their package is approved. The bell counts every area; the area's header shows its own count (N waiting check). A rejected package's values aren't counted.
- Sources N of M, in the area's header: how many of the area's regulated values (limits, setbacks, loading rates, flows ...) cite a source, counted over everything the area serves, the values it inherits included.
- When a plan prints its config check (an admin setting), it counts the same way: a plan designed on the area's current version shows the header's numbers.
- Catalog conflicts: pretreatment units or products whose values in an area's config and in the Products catalog disagree (size, flow, approval). Choose which one stands on the Catalog conflicts tab.
Areas and parts
On the Areas tab, the area list is on the left: Default, the country, its states and each state's counties. Type in Find a state or county to jump to one. The dot before each name gives its status: Verified by a licensed designer, Reviewed against sources, Unverified draft, Waiting check, or Uses Default (nothing of its own).
The Parts list beside it splits the area's config into parts:
| Group | Parts |
|---|---|
| Forms | Project Create (site details and limiting conditions), County forms (permit PDFs filled with the plan) |
| Systems | System types, Loading rates, Cross-section drawing (fields and limits per system), Pretreatment approvals, Approved products |
| Flow | Daily flow (the residential table and the commercial classes) |
| Map and parts | Components, Setbacks |
| Prices | Price book |
| Checks | Materials, References, Program classes (read only), Source audit |
Default and the areas below it
An area only stores what is its own. What it doesn't have comes from the area above it, up to Default:
- A county without its own Loading rates uses its state's, and a state without them uses Default's.
- A field a part leaves empty is filled from the same field above it.
- Setbacks, pipes and tank tables are taken whole: an area with rows of its own keeps only those.
The header of the area says what it Inherits from. A change to Default reaches every area that doesn't set the value itself.
Edit and publish a change
- Choose the area, then the part.
- Change the values. The header counts the unpublished changes.
- Click Review & publish. The drawer lists what changes and the checks. Fix any check marked !.
- Type What changed, in one line, for example the rule you followed.
- Click Publish and the new version. An admin's publish is Reviewed. A config approver can tick Publish as Verified with a license.
Publishing makes a new version of the area. To undo it, publish the previous version. Discard drops the unpublished changes.
To test an area before designers get it, click For everyone in its header to make it Admins only (testing). Everyone else gets the area above it until you release it.
How config values reach the design
The map loads the config of the project's area when the project opens. Details, the cross section editor, the hydraulic profile and the report PDF all read that same config:
| Where | What it takes from the config |
|---|---|
| New project | The site details and limiting conditions of Project Create. |
| Details, step 1 | The daily flow from Daily flow, the loading rate from Loading rates for the soil test, the tank sizes, and the systems System types allows. |
| Cross section editor | Each field of the Design form starts at its default in Cross-section drawing, and stays between its minimum and maximum. Fields the design doesn't set are listed under From defaults. |
| Hydraulic profile | Rules such as the sewer's minimum fall, the required distal head and the required vertical separation. In Where the values come from, these values are marked config, next to measured, entered, derived and default values. |
| Checks | The limits and design messages of the area, on the map, in Details and in the editor. |
| Report PDF | The calculations and references, the county forms, and the cross section and hydraulic profile sheets drawn from the design. |
| Cost estimate | The prices of the Price book, and the area's labor rates, fees and terms. |
| Map | The Setbacks of the isolation features and the Approved badge of products. |
A published change reaches new designs within about 10 minutes. A project keeps the version of its area's rules it was designed with: when the area publishes a newer one, the project shows Newer design rules. Review changes lists what the new version changes for that design. The designer can Keep the old version or Upgrade and recalculate.
Organization defaults change only an organization's starting values (Project Create, Cross-section drawing) and prices. Limits stay the area's.
The Legacy editor
Legacy editor in the area's header opens the old config dialog, for what Config Studio can't edit yet: flow rates, depth credits, component fields, the legacy loading rates, adding or removing a setback feature, and members' copies. Saving there writes your own copy only.
Served from… in the same header says which tables serve the area's projects: the new tables, or the legacy ones while an area is compared or switched back.
Related
- Details and the Report PDF
- Contour Systems: the cross section editor
- Cost Estimate
- Design Setup: a designer's own starting values