This message was deleted.

Can you elaborate a bit? Are you talking about access to documents in cloud storage accounts from Stacker (and maybe Airtable too?). My go to cloud storage solution is Box thanks to it’s enterprise class feature set and Airtable integration too. I’m currently exploring ways to provide internal users access to a folder on Box that is tied to each user record in Airtable but I don’t have enough progress on that front to report back yet. Or are you actually talking about being able to collaborate on a document that can be found and viewed via the Stacker app interface? I’d be interested in hearing from anyone using Coda integration with Airtable to provide document level access and features and thus some sort of possible connection to Stacker too.

I have an app that needs documents. The documents are in a SharePoint drive with heavy use of the meta data (no folders!). When a document is uploaded via Stacker to Airtable an automation is triggered in Airtable which calls a sequence in Make. This uploads the document to SharePoint and also to an Airtable base. Thus I mirror the SharePoint drive in Airtable. I use the automatic link in Stacker to link it to specific person IDs. The good thing is that I can delete the whole Airtable and still have all the structured data in the SharePoint drive (i.e. database based in meta data). Users can also delete documents via Stacker. I could replace the storage with something else if I need to or only keep a limited amount of data in Airtable but still have all in SharePoint. I am also interested in other ways to solve this.

@loud-magazine-63930 Yes, I am looking into what is possible with regards to both, 1. Access to documents in cloud storage & 2. Collaboration on documents I wanted to know if anyone has tried it, what is the User experience like. Would love to hear any updates on the Box access to users once you've worked on it. @great-air-35510 this is a great way to handle this. Can you tell me, do you have to give access to Sharepoint to each user? Something similar can be done with Google, but then the users' will need a Google email to access. Stacker lends itself to creating portals so easily, however a big part of client/partner/internal portals is sharing and working on documents. Any integration with these tools would be so beneficial!

@millions-army-64326 Users don't access the data in the SharePoint Drive directly. I created a SharePoint with permissions to access data anonymously and when the file is uploaded I generate the share link for the file and save this in Airtable. Users can access the file via this link and don't need to be logged into SharePoint. We need to give access to files also to people outside of the company. I can control this via Roles in Stacker. I can also delete the share link for each file and it will not be accessible from the outside. It is an ok solution for now. The SharePoint API is a pain so having the data available in Airtable makes my life easier. In case of a solution for Stacker you will need to find some cloud service that syncs the file database of the service to Airtable and make sure you have a link to access the file. CRUD operations will need to be added by some automations on your own via the middle layer called Airtable. You should make yourself clear, if you want to use a file storage or a DMS. You then either build the DMS yourself in Airtable/Stacker or mirror the DMS in Airtable. The latter let's me sleep better because if somehow my DMS layer in Airtable gets broken or deleted I can rebuild it with a click if a button.

Most of my use cases don’t have a need for the end users in Stacker to access files in the third party cloud storage solution. A typical workflow for them might be using the Airtable<>Stacker combo to fill out forms which then produce PDF files of those forms as they move through various phases of submission, approval and completion. Resulting PDF forms get stored and displayed in Stacker as needed but generally there is no end user collaboration going on with the document itself. The Airtable<>Box integration. in very useful for the internal team document management though. What it provides is an Airtable base of the complete Box file directory at whatever level you specify when nyou set up the integration. No complicated Make or Zapier scripting necessary. It gives you Airtable button-level access to any file out in that cloud directory. The Box filepath information gets added to the Box directory base in Airtable automatically, making it very. easy to navigate back to the source file. And of course you then have. full access to all the other feature rich integration options. that your Box account gives you, including the ability to open and. work on a given. document in a fully collaborative fashion. That includes both Microsoft and Apple software suites BTW. The view below shows how Box cloud storage is presented on a mobile device. Pretty easy to look up and work on a file from any device, but again, for my typical workflows, the web. portal end user is not a defined user on Box or any other third party app being used in the overall solution. Only internal team members, for example, would be defined users on the Box account. You can, of course define a publicly accessible file directory in Box and share that too, I just haven’t experimented much with doing that. I’d love to see a native Stacker table implementation of the same type of. Box integration that Airtable offers.