Most files in teamspace are Word or PDF documents – technically all the same at first. Through file classes you give them a business meaning: teamspace then knows that a file is, for example, an employment contract, an NDA or a data processing agreement. This is the basis for categorising documents, protecting them selectively and checking them for completeness.
Why file classes?
- Categorise: documents of one type are recognisable and findable system-wide – regardless of the file name.
- Protect: special protection and handling rules can be tied to a file class.
- Check: you can evaluate which element is still missing a document of a particular class.
Required files: “what’s still missing?”
Closely tied to file classes is the required files feature. With it you define which documents must be present on a customer, project or activity – and teamspace shows you where something is missing.
A typical example: you want to know which customer does not yet have an NDA or a data processing agreement on file. Via the file class, teamspace recognises the existing documents and makes the gaps visible.
Working together with templates
File classes and templates complement each other: from a template with placeholders you produce the missing document (e.g. the NDA) quickly and correctly pre-filled – and with the right file class it counts as “present” straight away.
ℹ Note (to verify). File classes and required files are described in the overview video as a property of every file. The actual setup (creating classes, defining required files per element type) sits in configuration mode and has not yet been checked against the live interface in this version (
last_verified: null). Details will follow once the UI paths are verified.
Related topics
- File management – introduction (with video) File management Introduction
- Working in the file manager File management How-to
- Set up file management (configuration) File management Configuration