
Use a preflight user comment to keep a photo-credit or creative-approval reminder attached to the relevant Affinity object. The comment creates a review prompt, not evidence that permission exists or that an editor approved the content.
Key Takeaways
- Preflight comments can identify object-specific human checks.
- The responsible person still needs to verify the underlying evidence.
- Clear a reminder only after recording the decision.
Attach the reminder to the right object
In current Affinity desktop, right-click the object or layer group and choose Preflight Comment > Set. Enter a concise instruction. The official preflight guide documents this workflow and lists copyright checking, creative approval and copy accuracy as uses.
Select the actual photograph or caption in question. A reminder attached to an unrelated group can become misleading when the layout is reorganized. Use an identifiable layer name when the project has many similar portraits.
Make the decision concrete
For a hypothetical exhibition booklet, a useful reminder might be “Confirm portrait permission for image P-017 with the project owner before public export.” It names the object, action and responsible workflow without placing confidential authorization records in the public caption.
A weaker reminder such as “check photo” leaves the next editor guessing. Keep the detailed evidence in the project's approved records and reference it according to normal access rules. Do not paste private releases or personal contact information into a deliverable unnecessarily.
Keep automated and editorial checks distinct
A green technical result cannot decide whether a credit is accurate or a person authorized a photograph. The preflight profile-scope guide reinforces the distinction between checked conditions and broader approval.
Likewise, a complete resource folder is not permission to publish its contents. Resource packaging addresses availability, while Affinity's embedding/linking help explains file dependencies. Neither establishes rights.
Close the reminder with a traceable review
Before export, review the comment in the Preflight panel, verify the required evidence and record who approved which revision. Clear the object comment when the decision is complete or retain an appropriate reminder if approval remains outstanding. Do not clear it merely to remove a warning.
If the booklet includes an approval form, give its controls meaningful labels; the photo-brief form-name guide covers that separate accessibility task.
Acceptance means the correct object was reviewed, the source of approval is recorded and unresolved items remain visible to the responsible editor. Inspect the exported file to ensure internal-only material has not been included through some separate production route.
This is a documentation-based reminder workflow. It does not offer legal advice, verify a license or claim that a preflight comment itself grants publication rights.
If the photo changes, reopen the approval question. Permission or creative acceptance tied to an earlier image does not automatically describe the replacement.
Related tasks
- Why Does InDesign Preflight Show No Errors When My File Still Has Problems?
- Why Are Images Missing When Someone Else Opens My InDesign or Photoshop Project?
- Why Does My PDF Announce Blank Fields Instead of Their Questions?
Sources and scope
- Preflight: Object-bound user comments preserve human review requirements.
Guidance follows current Affinity desktop documentation. Worked examples and checks are proposed, not measured software tests.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.