How to govern Adobe Firefly
Generative images and edits in your creative pipeline, and the provenance questions they raise.
Adobe · Reviewed when the vendor ships a capability change or a customer declares the tool
How Adobe Firefly is used
We see one common way businesses use Adobe Firefly, and we govern it on its own terms. If your team uses it differently, that is fine: you describe the use in your own words and Certrak works out the governance from what it actually does.
Image, video, or design creation
Consequence to people: LowGenerating images, video, or design assets
Internal informationEvery output reviewedCustomers, no decisions about them
Governing Adobe Firefly in practice
- Name one person who owns Adobe Firefly in your business. Governance starts with a name.
- Write down what Adobe Firefly is used for. Certrak recognises one common use: Image, video, or design creation. Yours may differ; write down yours.
- Decide what Adobe Firefly may and may not be given. Internal business information is in scope, so name what stays out.
- Agree that a person reviews every output before it is used, and name who.
- Look at this again twice a year, and sooner on any of these: industry incidents and vendor model updates.