# File Upload & Client Comms

**URL:** <https://community.glideapps.com/t/file-upload-client-comms/41082>\
**Category:** Ask for Help\
**Created:** [April 22, 2022, 6:24pm UTC](https://community.glideapps.com/t/file-upload-client-comms/41082 "2022-04-22T18:24:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![edan](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/edan/32/41743_2.png) [@edan](https://community.glideapps.com/u/edan)\
**Post date:** [April 22, 2022, 6:24pm UTC](https://community.glideapps.com/t/file-upload-client-comms/41082/1 "2022-04-22T18:24:39Z")

</div>

I’m using AirTable as the data source and looking to build a client portal.

Facing a few issues:

1 - I want clients to view files related to their project. Linking to files displays their url and not the actual file thumbnail.

 ![Screen Shot 2022-04-22 at 2.14.10 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/e/b/eb530e62b2e41d603b8b8d0e7df5c1e05e9c88fc.png)  
What’s the best way to approach this?

2 - Is it possible to allow a user to upload files without adding an entire form?

3 - Is it possible to allow client communication under respective projects?

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [April 23, 2022, 8:54am UTC](https://community.glideapps.com/t/file-upload-client-comms/41082/2 "2022-04-23T08:54:53Z")

</div>

> [@edan](#):
>
> I want clients to view files related to their project. Linking to files displays their url and not the actual file thumbnail.

I think you’re linking to the file itself, not a thumbnail URL that can be displayed as an image. I’m not sure if there’s an automatic way to do that.

> [@edan](#):
>
> Is it possible to allow a user to upload files without adding an entire form?

I think you can add a file picker pointing to a user-specific column, then a button to “Save” that file to the database, but I don’t know how you’re structuring your data though.

I assume you have a Projects table and a Files table. A project can have many files. In that case, the button will add a new row in the Files table.

> [@edan](#):
>
> Is it possible to allow client communication under respective projects?

You can add a table to store Comments, and relate them back to the Project by the Project ID field. Use the same approach as the file picker, show a text entry with a button to add a comment to the Comments table, and a collection to show all added comments.
