Resource types
Define the kinds of resource your workspace schedules — machines, people, tools, and anything else you run.
Configuration → Resource Types — the page is titled “Resources” and described as “Define the kinds of resource this tenant schedules, and the lists they carry”. Everything on it needs the administrator role.
Nothing is built in. A new workspace schedules nothing until you activate a type from the type catalog or define one here.
Creating a type
Add Resource Type:
- Name — the singular display name, for example Car. It labels one resource: the Edit Car row action, and the type’s slot on a request.
- Plural name — for example Cars. It labels a list of them: the page title, the type selector, the utilization filter. It is pre-filled from the name as you type and can be corrected, because not every plural is the name plus an s.
- Key — derived from the name, for example
car. “Lowercase letters, numbers, and underscores; must start with a letter.” Once the type exists the key is fixed: “The key identifies this type in links and stored data, so it cannot be changed.” - Icon — from the icon set. Shown in resource lists.
- Description — shown on the type’s page and on its resource dialog.
Under What these can do, three checkboxes decide how resources of the type behave:
- Can be placed on a floorplan — “Adds a code, a capacity and a drawable shape. Its site owns it and it cannot travel.” This makes the type a station, and puts it on Stations and on the site plan.
- Has directory details — “Adds an email, job title and department, and can be linked to a user account.” Use it for people.
- Belongs to one group at a time — “Adding it to a second group moves it, rather than listing it in both.”
A type that cannot be placed on a floorplan is an asset, and appears on Assets.
Every type is editable
There is no built-in badge and no locked type. A type you activated from the catalog is an ordinary type: rename it, re-icon it, change what it can do, change its fields, or remove it. Call your mills Machining centres if that is your vocabulary.
The two class checkboxes are the exception worth care. Turning off “Can be placed on a floorplan” moves the type from Stations to Assets and its resources lose their shapes.
Custom fields
A type carries its own fields. Open a type and add them: Text, Number, Yes/no, Date, Link, Choice from options you define, or a lookup into a shared list.
Fields belong to the type, so a mill can record a spindle speed and a tool changer count while a bench records neither. Values travel with the resource into search, import and export.
Criteria are a different thing and both still exist. A field records what a resource is; a criterion is the matched vocabulary scheduling uses. See Criteria and Capability matching.
Lists on a type
A type can also carry lists — a maintenance log per machine, for example. You define the shape of a list in List definitions and bind it to the type; editors fill it in from the type’s Lists tab.
Removing a type
Remove is protective. If resources of this type already exist, the type is deactivated instead of deleted so those resources keep working. A deactivated type drops out of the type selectors, the criteria applicability picker, and the Insights utilization charts. Its resources are left untouched. A type with no resources is deleted outright.
To delete a type and everything it holds, use the catalog’s delete path. See Type catalog.