Company Schema
Company Schema defines what a Workspace can know and which Actions can act on it. Start here to shape data before you create Records.
Boundary
Company Schema owns the model and its shared rules. Entities define kinds. Relationships define links. Interfaces define roles across kinds. Records & Lists owns the live values and groups built from that model. A schema change alters the rules those Records use. Governance & Administration owns access. Declaring a field does not grant access to its values.
Services
Company Schema separates the model from the logic that uses it. Choose the page for the object you need to understand before opening its change controls.
| Reader decision | Start with |
|---|---|
| Define a kind, link two kinds, or share a role across them | Schema model explains Entities, Relationships, and Interfaces. |
| Reuse a value rule, computed fact, selection, or function | Reusable logic distinguishes Value Types, Derived Attributes, Saved Queries, and Functions. |
| Change values or write to an external system | Actions and writeback explains effect ownership and readback. |
Start here
Company Schema opens at /schema in the Console. To change a kind, use Change schema safely for preview, approval, and readback. For work already launched, use Inspect action runs to check failed targets and pending effects. A builder can call ontology.listKinds to find the current model. Read the kind before choosing a change.
Next steps
- Schema model gives builders the rules for declaring a kind before Records use it.
- API reference gives HTTP callers exact permissions and inputs. Each native Surface guide owns its availability and syntax.
- API explains authentication and HTTP calls when a script needs Company Schema access.