# Visual proof of work/completion for tasks, how to approach?

**URL:** <https://community.fibery.io/t/visual-proof-of-work-completion-for-tasks-how-to-approach/5824>\
**Category:** Get Help\
**Created:** [February 9, 2024, 12:08am UTC](https://community.fibery.io/t/visual-proof-of-work-completion-for-tasks-how-to-approach/5824 "2024-02-09T00:08:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan\_Dejaegher](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ryan_dejaegher/32/8050_2.png) [@Ryan\_Dejaegher](https://community.fibery.io/u/Ryan_Dejaegher)\
**Post date:** [February 9, 2024, 12:08am UTC](https://community.fibery.io/t/visual-proof-of-work-completion-for-tasks-how-to-approach/5824/1 "2024-02-09T00:08:44Z")

</div>

Hi all, I’ve gotten into the taking short screen recordings and annotated screenshots to act as a visual aid and forcing function to consider tasks complete (_screenshots or it’s not done_)

I wanted to create a dedicated media/url field but it looks like you’re limited to one **Files** field in entities. This has led me to consider a few alternatives

1. Add the screenshot/video to files and add a tag to the task indicating that it has proof of work (I guess if it’s marked done, maybe it’s just assumed that it has a file)
2. Add it inline with the document
3. Create a database specifically for **Proof of Work** that’s linked to tasks

The thing that’s leading me to consider a separate database is that it doesn’t look like it you can create views/filters around the files. “Filter for tasks with proof of work field”

Anything I’m overlooking or overcomplicating with this approach?

---

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [February 9, 2024, 4:23am UTC](https://community.fibery.io/t/visual-proof-of-work-completion-for-tasks-how-to-approach/5824/2 "2024-02-09T04:23:08Z")

</div>

Fibery could benefit from both a new “single media” type field, and as you mention, the possibility to have multiple “Files” type collection fields.

These would be especially useful if you could drag-drop a file onto such a field in your browser – and/or paste there from your system clipboard – to upload.

This should be a Feature Request.

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [October 23, 2025, 1:34pm UTC](https://community.fibery.io/t/visual-proof-of-work-completion-for-tasks-how-to-approach/5824/3 "2025-10-23T13:34:54Z")

</div>

> [@Ryan\_Dejaegher](#):
>
> I wanted to create a dedicated media/url field but it looks like you’re limited to one **Files** field in entities.

Fixed in latest release

> [@October 23, 2025 / sauropod Multiple Files Fields per Database and some unexpected improvements](https://community.fibery.io/t/october-23-2025-multiple-files-fields-per-database-and-some-unexpected-improvements/9871):
>
> Multiple Files Fields per Database Now (and finally!) you can add multiple File Fields to any database and define whether each field allows one or many files. Previously, only a single File Field was supported, which created several annoying limitations. This update removes that restriction and our hands are free to improve files support in Fibery further person_getting_massage. Some new small things related to files in this release: Refined the File Field UI (a little bit) Added …