4ALLPORTAL4ALLPORTAL
All ideas

Let external recipients approve or reject files directly within a share

Users want to collect structured approval decisions from external recipients through a share, so that usage rights and consent are documented directly at the file level without manual follow-up outside the system. Problem / Pain: When external parties need to approve the use of files, for example confirming that images may be used for marketing purposes, this currently happens outside the system via email or phone. The approval decision is not linked to the file, must be entered manually afterwards, and is difficult to trace reliably over time. There is no structured, auditable record of who approved what and when, which creates compliance and governance risks for organizations that depend on documented usage rights. Impact / Benefit: Allowing external recipients to give structured approval or rejection decisions directly within a share would bring the entire consent and usage rights process into the system. Decisions would be documented automatically at the file level, traceable with a clear timestamp and identity record, and could trigger downstream workflows or metadata updates. This eliminates manual follow-up, reduces compliance risk, and makes usage rights reliably visible at all times. Example use case: A DAM manager shares a set of machine photos with an external customer and asks them to confirm whether the images may be used in marketing materials. The customer opens the share, reviews each image, and approves or rejects each one with an optional comment. The decisions are recorded immediately in the system and the approved files are automatically marked as released for marketing use with no manual data entry required. Idea source: Customer feedback Voting note: Vote for this idea if this need is relevant to you as well.

Activity · 0
productmanagementmarked this as Planned· 3w
productmanagementmarked this as In development· 5d

More in Collaboration & Workflow