Skills
Skills describe the capabilities, qualifications or equipment needed for work. Examples include First aid, Electrical work, English and Tail lift. Record what people, Vehicles and other resources provide using entries from the same catalog.
Your workspace has one skill catalog. Reuse its entries when recording what a resource provides or what work requires, so everyone uses the same terms.
Provided and required skills​
| Term | Meaning | Example |
|---|---|---|
| Provided skills | What a person or resource can contribute. | Anna provides First aid; a van provides Tail lift. |
| Required skills | What is needed to carry out work or use a resource. | A Tour requires First aid; a Vehicle requires a driving licence. |
A Vehicle can both provide and require skills. A van might provide Tail lift and require Driving licence. These are separate lists; requirements are compared with the provided skills available to the work.
Where you can record skills depends on the resource:
- People: assign skills to the user's profile through user management, with the appropriate permissions.
- Vehicles and custom records: use their provided- and required-skills fields. An administrator must configure those fields on the relevant definition before they appear on its records.
- Tours: select the Tour's required skills. Named Tour templates can save requirements for repeated work; applying a template copies its requirements when the Tour is created.
Defining a requirement records what is needed. It does not by itself assign people, allocate a Vehicle or verify that a person holds a certificate. The workflow using the skill determines how requirements are checked.
Set up your skill catalog​
Open Settings → Skills. You can search the catalog and, with the corresponding permissions, create or edit entries.
- Search for the capability first and reuse an existing entry when it means the same thing.
- Choose Create skill and fill in the two fields below.
- Save the skill, then select it on the relevant person, resource or Tour. Creating the catalog entry does not assign it anywhere automatically.
| Field | What to enter | Example |
|---|---|---|
| Name | A clear display name, unique within the workspace. | First aid |
| Short Key | An abbreviation of at most 6 characters, unique within the workspace (upper and lower case count as the same). | FA |
Use specific names when distinctions matter, such as separate licence classes. A skill's name does not create special behavior: calling a skill “Required” does not make it mandatory, and calling it “Vehicle” does not make it a system-defined skill.
Keep people's and resources' skills up to date. Editing a catalog entry changes the shared entry; it does not create a separate copy for each place that uses it. Review its use before deleting it.
Skills and permissions​
Skills describe capability. Roles and permissions determine what a person may see or change. Giving someone Electrical work, for example, does not give them permission to edit Tours, assign Vehicles or change Device settings. Likewise, being able to manage the skill catalog does not automatically grant permission to edit every person's or Vehicle's skills.
If the Skills page or an editing action is unavailable, ask your workspace administrator to check your permissions.
How Tour requirements work today​
Standard Tours store the selected requirements, and named templates can supply them to new Tours. Requirements can be edited until the Tour finishes. They do not currently select participants or automatically enforce participant eligibility. Review the team and its capabilities when planning.
Specialized workflows, such as those provided by workspace plugins, can have their own skill checks. Their rules are separate from the standard Tour behavior described here.
System-defined skills​
System-defined skills have a specific meaning maintained by Tourfold. They are distinct from skills created by your organization or supplied as sample data.
There are currently no protected system-defined skills in the standard catalog. The following skill is planned for the Tours and Vehicles integration:
| Skill | Provided by | Meaning when required | Availability |
|---|---|---|---|
| Vehicle | Every Vehicle, automatically. | At least one eligible Vehicle must be assigned before the Tour can start. | Planned; not yet available. |
When this feature is available, Vehicle will appear in the normal Skills list and requirement selectors with a System managed badge. You will not need to assign it to each Vehicle. It will also apply when a Vehicle definition has no editable provided-skills field.
Its short key is VEH, so no other skill in the workspace can use that short key. The system skill cannot be renamed, edited or deleted. Tourfold manages its provision automatically; you cannot manually assign or remove it as a provided skill. You will still be able to add or remove it as a requirement on editable Tours and templates. A customer-created skill with the same name will remain an ordinary skill and will not satisfy the system Vehicle requirement.
Plugin-managed skills​
Some workspace plugins rely on specific skills, for example to recognize a driver role or a licence. When such a plugin is enabled, it adds those skills to your catalog. They appear with a Plugin managed badge.
- The plugin recognizes these skills by their short key, so you cannot rename them, change their short key or delete them.
- You can assign them to people and resources and select them as requirements, like any other skill.
- Enabling the plugin fails while a skill you created already uses one of its names or short keys. Rename that skill or change its short key first.
A skill you create yourself never becomes plugin-managed, even if it has the same name.
Using skills with Tours and Vehicles​
Planned functionality
The following coverage checks and the Requires a Vehicle setting are part of the planned Tours and Vehicles integration. They are not available in the current standard Tour workflow.
The planned workflow will compare requirements with the skills contributed by the Tour's participants and assigned Vehicles:
- The provided skills of participants and assigned Vehicles will be combined. Anna can provide First aid, Ben Electrical work and the van Tail lift; no single person or resource needs every skill.
- A requirement will be covered when the same skill is provided by any of them. This applies to requirements from both the Tour and its Vehicles. There is no setting restricting an ordinary skill to people or Vehicles: if a resource is recorded as providing it, it counts.
- Only people and Vehicles participating in the Tour will count; associating a phone with a Vehicle will not add its user to the Tour. No driver–Vehicle pairing will be required.
- Requirements will show where they come from, for example Driving licence required by BW-1. Removing that Vehicle will remove its contribution; a requirement also specified by the Tour or another Vehicle will remain.
Use separate skills for different meanings, such as First-aid training and First-aid kit. Tourfold matches the selected catalog entries; it does not infer a provider restriction from their names. The system-managed Vehicle skill keeps its automatic provision described above.
Example: a maintenance team​
A Tour requires First aid and Electrical work. Anna has First aid; Ben has Electrical work and the licence required by van BW-1. The van provides Tail lift and the system Vehicle skill. Together, Anna, Ben and BW-1 cover these requirements without making the van belong to either person.
If Ben is removed before the Tour starts, the missing Electrical work and licence requirements will appear as warnings. The participant list is fixed once work starts. Missing ordinary skills, including a Vehicle-required licence, will not block an otherwise valid start. Skills will continue to describe recorded capabilities; Tourfold will not verify the underlying qualification documents through this feature.
Requiring a Vehicle​
Requires a Vehicle will select the system Vehicle skill in the Tour's requirements. One eligible assigned Vehicle will satisfy it; a remembered phone association alone will not. A missing required Vehicle will block the initial start. If an authorized participant removes the last Vehicle after the Tour has started, the Tour will remain usable and finishable with a warning.
The setting will also be available on Tour templates. Put it in the Default Tour template when Tours created without a named template should normally require a Vehicle. A named template will use only its own requirements. Template changes will affect new Tours, without changing existing ones or preassigning a particular Vehicle.