Usage and rights
The four settings that reach the manifest — and why "no statement" is not the neutral choice.
Settings → Content Credentials holds two cards: „Nutzung durch Dritte“ (Third-party usage) and below it „Urheber und Rechte“ (Creator and rights). Both write into every manifest your workspace signs.
Only owners and admins can change it. Members do not see the „Einstellungen“ menu entry; reading the values is permitted to every role.
The signed-in product speaks German, so its labels are quoted in German throughout, with the English rendering in italics.
The four settings
| Setting | What it covers |
|---|---|
| „Training generativer KI-Modelle erlauben“ (Allow generative AI training) | Models that can produce new images or videos from it. |
| „Training sonstiger KI-Modelle erlauben“ (Allow other AI training) | Non-generative models, e.g. for object recognition or classification. |
| „Data Mining erlauben“ (Allow data mining) | Automated analysis for patterns and correlations, without training a model. |
| „Nutzung als Eingabe für ein fertiges KI-Modell“ (Use as input to a trained model) | Three-way: „Keine Angabe“ (no statement), „Erlaubt“ (allowed), „Untersagt“ (prohibited). |
The first three are switches, the fourth is a choice of three.
The inversion worth knowing
The switches ask about permission — what gets stored and published is the prohibition.
So a switch that is off does not stay silent. It writes an explicit "not allowed" entry into the manifest. The three switches are always present in the manifest, even when everything is prohibited.
Only the fourth setting is ever omitted: „Keine Angabe“ drops the entry from the manifest entirely. The value is not published as "no statement" — it is not published at all.
Omitting is not the same as a neutral statement. Most evaluators treat a missing entry like a permission, and the standard does not define how a missing entry is to be read.
A workspace that never opened this page therefore publishes: three prohibitions and no statement on the fourth setting.
What this is and what it is not
The explainer says it in one sentence: „Das ist eine Willenserklärung, keine technische Sperre.“ (This is a declaration of intent, not a technical block.)
It works towards third parties who honour the standard. It stops nobody from using the file anyway — it only makes the statement machine-readable and signed.
When the value is read
When the render job is queued, not when you save. The application reads your setting fresh as it queues the job. A change triggers no re-render.
The page says:
Die Einstellung gilt für künftige Signaturen. Bereits signierte Derivate behalten die Aussage, die zum Zeitpunkt ihrer Signatur galt.
The setting applies to future signatures. Derivatives already signed keep the statement that applied when they were signed.
Where you find the statement again
Only in the manifest. It appears on no asset and in no verification result — the report knows the editing chain and its ingredients, but no usage statements.
To see it on a particular file, download its manifest: „Content Credentials (JSON)“ in an output's menu, „Manifest herunterladen“ on the quick check's result card.
Careful with the original: downloading the source file's manifest gives you the foreign manifest it arrived with — that one knows nothing of this setting.
The record
Every change is written to your workspace's audit trail with the four new values.
Creator and rights
The second card has three fields, all optional and all empty to begin with:
| Field | What belongs in it |
|---|---|
| Urheber (Creator) | Who made the picture — a person or an organisation. |
| Copyright-Vermerk (Copyright notice) | Who holds the rights. The name only; verstag puts the © and the year in front when signing. |
| Credit-Zeile (Credit line) | Who should be named when the picture is published. |
What you leave empty is not in the manifest. verstag puts nothing there on its own.
The values apply to everything signed in this workspace. If you work for several clients, leave them empty — a value that is right for one of them would be wrong for the others.
At most 200 characters per field. Line breaks are refused.
What can go wrong
The save button stays grey. It is disabled until something has changed.