Types
Three "type"-shaped concepts run through FlecBase. Knowing which is which makes the platform behave intuitively; confusing them is the most common source of "why isn't this showing up where I expect" friction.
Entity types are the fixed, system-managed top-level shapes — Person, Organisation, Asset, Event, Order, Incident, Inspection. You can't add or remove them; they're the table-level concepts the platform is built around.
Subtypes are the editable labels you apply to a record within an entity type. A Person's subtype might be "Customer", "Employee", "Volunteer". An Organisation's might be "Client", "Supplier", "Site". Subtypes are per-tenant — your workspace's subtype catalogue is yours to manage. The platform seeds a sensible default set on signup; you add / hide / rename to suit how your business actually talks. Throughout the UI you'll see "type" used as the user-facing word for what the schema calls "subtype" — they're the same thing.
Relationship types are different again — they describe the connection between two records, not the records themselves. "Employee of", "Contractor for", "Client of", "Subsidiary of" are all relationship types. They drive which panels a record shows up in (e.g. the Contacts panel on an Organisation) and how records appear when you walk a graph.
The rest of this page covers the system defaults, what changing a type does on the fly, and where each lives in the admin portal.
types_1.png