Project fields

Project fields are details every project can carry, a client or a campaign, say. You define the fields under Settings → „Projektfelder“ (Project fields). They are filled in per project under „Projektangaben“ (Project details) in the project’s menu — see Projects.

In filenames the values appear through the placeholder {meta.<key>}, see Export naming. They never reach a file’s Content Credentials.

The signed-in product speaks German, so its labels and messages are quoted in German throughout, with the English rendering in italics.

Only owners and admins may create, rename and delete fields. A member gets a 404 page. Every member may fill them in.

The page has two cards: „Projektfelder“ with the list at the top, and „Neues Projektfeld“ (New project field) with the form below it.

Creating a field

A field has two parts:

• „Bezeichnung“ (Label) — what the field is called in the project details and in a project’s header, „Kunde“ (Client) for instance. At most 60 characters, unique within the workspace regardless of case.
• „Schlüssel“ (Key) — what the field is called in a template: the key kunde becomes the placeholder {meta.kunde}. It is suggested from the label, kampagne_2026 from „Kampagne 2026“ for instance, and can be overwritten.

The key:

• uses only lower-case letters a to z, digits and _
• starts with a letter
• has at most 32 characters
• is unique within the workspace

The key cannot be changed once the field exists; the label can.

A workspace has at most 20 project fields. Once it has that many, „Feld anlegen“ (Create field) is disabled.

Three messages when creating a field:

• „Den Schlüssel „kunde“ gibt es in diesem Arbeitsbereich schon.“ (The key „kunde“ already exists in this workspace.)
• „Ein Projektfeld mit dieser Bezeichnung gibt es schon.“ (A project field with this label already exists.)
• „Höchstens 20 Projektfelder pro Arbeitsbereich.“ (At most 20 project fields per workspace.)

The list

Each row shows the label, the placeholder and how many projects have the field filled in — „in 3 Projekten ausgefüllt“ (filled in for 3 projects) or „noch nicht ausgefüllt“ (not filled in yet). Deleted projects do not count.

„In Vorlage verwendet“ (Used in a template) marks a field whose placeholder appears in an export template — the workspace’s or a project’s, a deleted one’s included.

„Umbenennen“ (Rename) on the row changes the label only. Values and templates hang on the key and stay as they are.

Deleting a field

Deleting removes the field and its value in every project, deleted projects included. Where the field has values, the confirmation says in how many projects they will be lost.

A field that an export template uses cannot be deleted — „Löschen“ (Delete) is disabled then. That holds for the workspace template and for every project’s, including a project under „Gelöschte Projekte“ (Deleted projects) until it is deleted permanently: by hand, or once its 30 days have passed.

To free the field:

• Workspace template: take the placeholder out of the template under Export naming.
• A project’s template: remove the placeholder under „Projektangaben“ on the project, or choose the workspace template.
• Deleted project: restore it and change the template, or delete the project permanently.

In the audit trail

Creating, renaming and deleting a project field are recorded in the administration trail: „Projektfeld angelegt“ (Project field created), „Projektfeld umbenannt“ (Project field renamed) and „Projektfeld gelöscht“ (Project field deleted). Values never appear there. More under The two audit trails.