Display Adobe generative AI content credentials stored in asset metadata

Users want to see whether an asset was created or edited using generative AI tools directly in the system, so they can identify AI-generated or AI-modified content without leaving the platform. Problem / Pain: When creative teams use generative AI tools to create or edit images, information about this may be written into the file's metadata by the tool. However, this information is currently not surfaced in the system. Users who want to identify which assets were created or modified using generative AI have no way to see this directly and would need to open each file in an external application to check. Impact / Benefit: Displaying AI content credential information stored in asset metadata would give teams immediate visibility into which assets involved generative AI, directly within their normal asset management workflow. This supports transparency, informed content decisions, and compliance with emerging standards around AI-generated content disclosure. Example use case: A DAM manager wants to identify which images in a campaign collection were edited using generative AI tools. Instead of opening each file individually in an external application, they can see the relevant content credential information directly in the asset detail view within the system. Idea source: User feedback Voting note: Vote for this idea if this need is relevant to you as well.