CartVisualAssets & tasks / DECISION GUIDE
How to separate private support evidence from a public creative example
Keep the private problem report and the public teaching example separate. Support needs enough detail to find the task and the defect. A public reader needs a clear lesson. Sharing a file for help does not, by itself, give permission to publish it.
Choose what each reader needs to see
In this fictional case, a jewelry photo has a customer’s name engraved on a charm. A generated result adds an extra clasp. The name does not explain the clasp defect. A public article should not expose it merely to show that something went wrong.
For support, describe the expected clasp, the extra clasp and its location. Add the available task reference. The defect-report guide explains how to locate a visible problem without guessing its cause. Do not pay for another generation just to make the report look complete.
Use three files for three different jobs
| Example file | What it contains | Who should see it |
|---|---|---|
| J0: original | Untouched source and result, including the name | Only people with a necessary, agreed private purpose |
| J1: marked copy | An arrow at the extra clasp; unrelated details removed as appropriate | The agreed support recipient, if a media-sharing route is needed |
| J2: public teaching example | A separately permitted fictional product with a neutral engraving | Public readers after a new permission and export check |
J0, J1 and J2 are invented labels. No customer files were inspected. Save J1 as a copy so its arrow does not replace J0. Label J2 “illustrative example”; it must not be presented as the actual customer incident.
J1 may still contain private information. Removing the name does not automatically make the whole image public. Check the product, other identifiers and the rights for the planned audience.
Use the feedback form as it actually works
The current CartVisual form accepts a subject, description, category, feature and optional task reference. It does not upload image attachments. Its saved task summary keeps selected diagnostic fields separate from private generation instructions. Mentioning J0 in the text does not attach J0.
Leave out passwords, API keys and full payment details. If support later agrees a route for media, send only what that investigation needs. Check what a shared link lets its recipient open, not just its thumbnail. Frame.io’s sharing controls provide an external example of explicit access choices; they are not CartVisual controls.
Inspect the exported copy after hiding private details
Open the file you plan to send. Is the customer name still visible in another frame, thumbnail or crop? Does the clasp remain clear enough to explain the issue? If privacy and useful evidence cannot both be preserved, use an approved fictional example for public teaching.
A box drawn over a name in an editing project may be removable. Check the final export in a normal viewer, not only the editor’s working view. Also follow the public-file metadata review: a clean-looking image can still carry private file properties. Preserve required rights or AI-origin information rather than stripping every field blindly.
Make a fresh decision before public use
Confirm who can approve the product photo, any depicted person and the proposed public use. Access for a private investigation is a different decision. A support administrator’s ability to open a report does not grant marketing rights.
For this exercise, the private report keeps the actual task and clasp location. The public article uses J2 and says it is fictional. Keep the original record restricted. If another export or a new public use is proposed, check that exact file and scope again.
Sources and further reading
Sources for this page were checked on . Platform rules can change; verify the current source before publishing. Prompt examples and workflow recommendations are CartVisual editorial guidance, not independently measured results.
Frequently asked questions
Does the feedback form attach a photo when I name it?
No. It accepts text and an optional task reference, not image attachments.
Is a marked or redacted support copy automatically public?
No. Check remaining private details and obtain permission for the specific public use.
Should the anonymous public example look like a real customer case?
Label a fictional replacement as illustrative. Keep it separate from the actual private investigation record.
PREPARE ASSETS FOR YOUR NEXT STEP
Create supporting product assets in CartVisual.
Create new product creative assets in the workspace, then continue in your chosen tools. Third-party software procedures described in this guide take place in those applications; this workspace link does not imply an integration. Check current capabilities, account access and credit quotes.
Explore asset creation tools Check pricing and credits