Configure
Designer · Funding Allocations WF
Publish your business processes on Tuesday. Don’t wait two years for professional services to do it.
Owner-side teams stay on a legacy PMIS for one reason that is not the UI. They fear the next system cannot take their cost codes, numbering, workflow and RBAC without a systems-integrator programme.
TerraForge Configure is that depth, in the product. The Administration tree is live. You do not raise a change request to publish a business process.
Administration
The live admin tree — not a settings dump.
Company Configuration. Cost Codes, Cost Columns, Exchange Rates, Cash Flow Curves. Fund Codes. Record Numbering. Integrations. Users, User Access, Security Groups. Workflow Engine, Form Configuration, Data Elements, App Builder, Custom Output, Shared Views. Data Hygiene. This is what a legacy PMIS administrator opens on day one.
Company Configuration
Brand, currency, region — set once. Every money field reads it.
Legacy PMIS administrators already know where company properties live. TerraForge puts them in the same conceptual place. Currency and region are organisation settings. The Cost Sheet, Fund Sheet, portfolio and every published app read them. Dated FX on the sheet. Not a per-project workaround. Not a vendor ticket.
Dashboard Settings
Widgets, tabs, wall display, reorder. Summary versus Asset, Lease, Project or Field. A new chart is configuration, not a statement of work.
Cost Sheet configuration
Cost codes and columns — the arithmetic the Cost Sheet actually rolls.
If the cost structure cannot be yours, the rest of the PMIS is theatre. An administrator sets the Cost Codes — the hierarchical WBS — and the Cost Columns the sheet computes: Initial, Changes, Transfers, Revised, Committed, Actual, Forecast, Remaining.
Exchange Rates and Cash Flow Curves
Multi-currency is a company setting. The rate on the sheet is dated. Curve definitions Cash Flow Manager applies to a Cost Sheet column. Steepness and skew live on the curve — not in a planner’s spreadsheet for the monthly pack.
Funding Manager
Fund codes and Fund Sheet columns — colors of money, configured.
Capex is not a government grant. A grant is not a PPP. Fund Codes carry type and currency onto the Fund Sheet. Fund Sheet Columns decide what the sheet shows — revised value, pending and approved requests, remaining, pending demand.
This is the admin half of Funding Manager. The live sheet the controller opens is on the Product tour.
Record Numbering
Configurable prefixes per business process — on create, not later.
SCH-, WO-, CNT-, LEA-, the app you published last Tuesday. Numbers land when the record is created. You do not bolt a numbering scheme on as an integration six months after go-live. Legacy PMIS people will look for this on day one. It is here.
User Mode Navigator is the left-hand nav users actually see. Group business processes, set order, hide what a role does not need — without a second product.
Integrations
Open REST, webhooks — and P6 by XER or both ways.
Every published app is on an open REST API — scoped keys, allowed-apps restriction, optional expiry. HMAC-SHA256 webhooks are thin: field data does not leave on the envelope. Primavera P6 comes in by XER, or one-way or bidirectional over REST and webhooks — on Schedule Manager.
User Administration
Users, access, security groups — three-tier RBAC with programme scope.
A PMIS that cannot answer “who can see this project?” does not survive an owner-side security review. TerraForge ships Users, User Access and Security Groups as first-class Administration.
Roles — admin, manager, viewer — plus per-module None / View / Edit / Admin. Users inherit the highest level across every group they belong to. View Groups on programmes and projects; child records and dashboard widgets honour the same gate.
Audit — what changed?
Immutable trail: every create, update, delete, login and import. Click a row and the panel is a field-level diff — what it was, what it is, who, when. Completed workflow fields lock; the API refuses the write. The control list is on Security.
TerraForge Designer
App Builder, forms, data elements and workflow — this is where they live.
This is the capability most enterprise PMIS products apologise for not having. In TerraForge it is Administration — not a side tool and not a consultancy engagement.
App Builder composes a business process from the Data Elements library — sections, a form, a workflow binding — then publishes. RFI, Daily Report, Site Incident, Initial Budget, Contracts, Payment Applications: they are apps. Publish on Tuesday. The team is in it on Wednesday.
Workflow has its own section below: production-ready processes on day one, and a visual designer when the approval path is yours.
Forms, Data Elements, Shared Views, Custom Output
Form Configuration is the form the business process actually opens. Data Elements are one typed field library. Shared Views let an administrator publish the default. Custom Output is Word mail merge: drop {{ field }} tokens, test-render, activate.
Workflow Engine
You are not starting from a blank canvas.
TerraForge ships production-ready workflows on the business processes legacy PMIS teams already live in. Go live without a blank page — then open the same designer to extend them, or build the approval that does not exist yet, without code.
Data Hygiene
Orphans, missing keys, dirty load — in TerraForge, not a spreadsheet.
A design-partner launch dies on dirty data. Data Hygiene is where the administrator sees foreign keys pointing at missing documents, orphan workflow tasks and required-field gaps — in the product, not after the load.
Recompute usage on Data Elements. Purge test pollution. Open the broken work order and fix the asset or vendor it still thinks it has. The same place legacy PMIS people look when they ask whether you can run a clean go-live.
See it running against your own programme data.
Not a canned demo environment — your business processes, your data.