A catalog entry can carry `restrictToOrgId`. The library filters entries so a restricted template is visible only to the org it belongs to. This is how a builder's actual signed-off contract (e.g. the Graber Custom Structures three-part agreement) becomes a one-click preset they can duplicate per building type.
Also called: client-confidential contract · restricted template · our own contract in the library
- 1The catalog entry declares restrictToOrgId.
- 2ContractTemplateLibrary filters: `CATALOG_TEMPLATES.filter(t => !t.restrictToOrgId || t.restrictToOrgId === currentOrgId)`.
- 3The current org is resolved from /api/me, so a mis-set id hides the template rather than exposing it.
Straight from the code: 'restrictToOrgId pins this to GCS only — no other tenant sees their legal text in the library.' A builder's contract is their own competitive and legal work product; loading it as a shared catalog entry would have published it to every other builder on the platform.
- Onboarding a builder who already has attorney-approved legal text
- Keeping one tenant's legal wording out of every other tenant's library
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →