Place - Flagging AI content

More organizations are being asked — by regulation, by clients, or by their own governance policies — to know which of their assets involve AI, and to disclose that clearly where it matters. Without a consistent way to record this, that information lives in people's heads, or nowhere at all. The AI Content Field lets you flag AI involvement directly on an asset, so it's recorded, visible, and easy to find.

Read more about the AI EU Act here 

Why use the AI Content Field?

• Regulatory disclosure — flag AI-generated or AI-modified content so your team can meet transparency obligations that apply to your organisation
• Internal governance — keep a consistent record of where AI has been used across your asset library, without relying on memory or side documentation
• Downstream consistency — because the field uses a standard, recognized set of values, other systems your assets pass through are more likely to recognize the label too

Who can use it?

The AI Content Field is available by default — there's nothing to enable, and no setup is required to start using it.

If you'd like to change how it behaves for your organisation, contact your Customer Success Manager to:

• Make the field mandatory on upload
• Hide the field entirely for your organisation

How it works

Flagging an asset

1. Open the asset in Place
2. Locate the AI Content field
3. Select the value that describes the asset
   1. Unknown - this is the default on upload 
   2. No AI used 
   3. AI generated 
   4. AI modified 
4. Save the asset

Once set, a visual badge appears on the asset thumbnail and in the asset detail, so anyone browsing the library can see its AI status at a glance without opening the asset.

Finding AI-flagged assets 

A new filter will be available where you can filter assets by any of these states. Combined with bulk editing, this helps administrators audit and maintain the accuracy of the asset classifications.

Note: If mandatory upload is enabled for your organisation, users won't be able to complete an upload without setting this field.

Preserving AI provenance on original assets

Some AI-generated content already carries signed provenance credentials (such as C2PA) from the tool that created it. When you upload this kind of asset, Place preserves that signed metadata intact — it isn't stripped out as the asset moves through the platform.

This means the original file keeps its verifiable AI provenance information for as long as it stays in Place.

Using this with Produce

The AI Content Field value you set on an asset carries through to Produce. When your team builds documents using flagged assets, Produce surfaces this information so you can decide, at the point of production, whether a piece of output needs an AI label or disclaimer added — rather than having to check each source asset separately.

This is intended to support your team's decision-making, not to make that decision for you. Whether a given output actually needs a label is still a judgement call for your team.

We're continuing to build on this capability, with more coming soon.