Type catalog
Switch on the kinds of resource your shop runs — mills, lathes, stations, people, tools — or hide and delete the ones you do not.
Configuration → Type catalog — “Pre-configured manufacturing resource types. Switch one on and it becomes an ordinary type with industry-typical fields — rename it, change its fields, or remove it like any other.” Administrator role.
Orkyo ships no resource types. The catalog is a starting point: a set of types that already know what a shop usually records about them, so you do not build a mill from an empty form.
What the catalog offers
Each entry names a kind of resource and arrives with the fields that kind usually carries — a mill with a spindle speed and a tool changer count, a test station with its test types and a calibration date, a person with a badge number.
An entry shows its icon, its description, how many fields it brings, and its state. An entry your workspace renamed keeps a badge saying so, so you can still find the mill you now call a machining centre.
Activate a type
Switch the entry on. Orkyo creates the type with its fields and the type appears immediately on Stations or Assets, according to whether it can be placed on a floorplan.
From that moment it is an ordinary type. Nothing about it is protected: rename it, change its icon, add or remove fields, or edit what it can do. See Resource types.
Activating an entry your workspace already has adopts the existing type rather than making a second one. A type you deactivated earlier comes back with its resources intact.
Hide a type
Switch an entry off. A type with no resources is simply removed.
A type in use needs a decision, and Orkyo asks for it: “This type is in use: {n} resources reference it. Hiding keeps all data and the type can be switched back on later. Deleting removes the type together with its resources, their assignments and booking history, its groups, and its request targets.”
Hide type keeps everything. The type stops appearing in selectors, pickers and utilization charts, and its resources stay in the database. Switch it back on and they return.
Delete a type and everything it holds
Delete everything… is the other answer, and it has a second confirmation of its own naming what goes: the resources of that type, their assignments and booking history, every group of the type, and its request targets. Requests survive, with that type removed from their targets.
This cannot be undone. There is no export step inside the flow, so take one first if the data matters — see Import and export.
When no type is active
A workspace with no active type cannot schedule anything, and the product says so where it matters rather than failing quietly. Request creation refuses with a message pointing here, and the spreadsheet import stops rather than inventing a type.