How the help center is built
How we classify articles
At its core the help center is one large collection of individual articles. Each article exists exactly once and is described by several criteria. All pages - topics, processes, purposes, search - are just automatic views on these criteria. No duplicate content, but many ways to the goal.
The criteria are ordered here by their importance for classification - from "what is it about?" through "who is it for?" to the technical and automatic ones.
Topic
What is it about, in terms of content?
The most important criterion - and the main entry point in the help center. Topic blocks are an independent structure, separate from the product modules: a large sub-topic like the calendar may get its own block even though it technically belongs to "Teamwork". Every article belongs to exactly one topic - its content home.
Possible values
- Basics
- Project management
- Time tracking
- Capacity
- Open items
- CRM
- Sales opportunities
- Ticketing
- Invoicing
- Product management
- Costs & travel expenses
- Personnel & HR
- Workplace
- Calendar
- Boards
- Wiki
- Forum
- File management
- Quality management
- Controlling
- Key figures
- Permissions
- API
- teamSync
- Installation
- Configuration
- Configuration search
- System configuration
Count & required: Exactly one value, required.
Purpose (article type)
What kind of information is this?
Determines tone and expectation: a quick how-to to follow, an explanatory concept to understand, the technical reference to look things up, or a guided introduction. It also defines where the article is stored.
Possible values
- How-to
- Concept
- Reference
- First steps (learning path)
- Cross-topic
Count & required: Exactly one value, required.
Modules
Which teamspace modules does it belong to?
The product view. It connects the article to the matching function pages on teamspace.de. In the help center the topic leads navigation - the modules are cross-references. An article may touch several modules (a cross-cutting concept, say time tracking and invoicing) or none (e.g. general basics).
Possible values
- Time tracking
- Project management
- Invoicing software
- CRM
- Service Desk
- Teamwork
- HR software
- Workplace management
- Quality management
- Cross-cutting
Count & required: Several possible or none, optional.
Processes
Which business process does it support?
The steering view - especially for management and partners. An article can contribute to several of the seven core processes. The process role says how central it is (lead = central, support = relevant but secondary).
Possible values
- Sales process
- Project delivery
- Billing process
- Cost control
- Customer care
- Employee process
- Business management
Count & required: Several possible, optional (may be empty). Each with role lead/support.
Audience
Who is the article written for?
Helps frame the same matter for different readers - the user wants to click, the admin to configure, the decision-maker to understand.
Possible values
- User
- Admin
- Decision-maker
Count & required: Exactly one value, default is "User".
Availability (edition/product)
Where does the content apply?
Marks which products or editions a content applies to. If the field is empty, the article applies in general.
Possible values
- office
- enterprise
- projectfacts
Count & required: Several possible, optional. Fixed values.
Effort & complexity
How much effort is the implementation?
Helpful especially for how-tos and learning paths: a difficulty level and a rough time estimate for the task. Usually empty for concept and reference articles.
Possible values
- easy
- medium
- complex
- + task duration as a time estimate (e.g. "~5 min")
Count & required: At most one value each, optional.
Technical details (reference only)
Which technical details belong to it?
Only for reference articles: the technical area and - for API articles - endpoint, HTTP methods and authentication.
Possible values
- API
- Installation
- teamSync
- Configuration
Count & required: Area is required for reference, omitted for all other article types.
Determined automatically
What does the system calculate itself?
Nobody maintains these by hand. Reading time is estimated from the text length; "contains video" follows from whether a video is attached. The check date, by contrast, is maintained manually and shows how current the article is.
Possible values
- Reading time (calculated)
- Contains video: yes/no
- Checked on: date (manual)
Count & required: Reading time and video automatic; check date maintained manually.
Planned (full build)
What is added later?
In the bilingual full build, every article gets a language (German/English), and version-dependent content gets a product version. Neither is active yet.
Possible values
- Language: German / English
- Product version (e.g. "2026.1")
Count & required: Not active yet.
At a glance
| Criterion | Values | Required? |
|---|---|---|
| Topic | one | required |
| Purpose | one | required |
| Modules | several/none | optional |
| Processes | several | optional |
| Process role | one | optional |
| Audience | one | required (default User) |
| Availability | several | optional |
| Complexity | one | optional |
| Effort | one | optional |
| Reference area | one | required for reference only |
| Reading time | one | automatic |
| Contains video | one | automatic |
| Checked on | one | maintained manually |
Why this effort? A clean classification makes the help center findable for people across many paths - and machine-filterable for AI, e.g. "all how-tos on the billing process in the Invoicing topic, for admins, with video". Only a minimum is deliberately required (topic, purpose, module, audience); everything else may grow with the content.