View Only File withing View/Edit Folder

(0) Share

Report

Posted on by adriennevh

I'm trying to use PA to create a public drop box folder with files within which are view only. ie people can add files to the folder, but then their permission is taken away and they can only view that file, but can continue to add documents.

I am creating a view/edit sharing link for the folder.

Then using HTTP request, breaking inheritance on the file. (I'm not sure if the 'stop sharing' Action is the same)

Then creating a view only sharing link for the file.

However, if i send the Folder link, the file is still view/edit. If it send the file link, it's view only. If that person then opens the folder link AFTER opening the file link, that file is successfully view only. But that is too many steps.

How can i allow people with the folder view/edit link to view only the files inside it?

I imagine i want to be able to 'shre everything in this folder even with unique permissions? but I cant.

I do have 'anyone with the link can view' permission to share.

I have no idea how to get this to work.

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Pstork1 69,022 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

The problem is that the Stop Sharing and Create a Sharing Link doesn't actually change the item level security. To do what you want you need to do everything using HTTP REST calls.

1) Break Security Inheritance and don't replicate permissions.

2) Set Item Level permissions for the person or Group to View Only permission level.

This is the HTTP REST call for setting Read Only permissions

You don't need the sharing link at all.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
Building with Why 351 Moderator on at

Like (0)

Report
Copy link

Link copied!

One option would be to use a per Flow license and have a service account with higher permissions create the folder. Then you don't have to break down the folder permissions or worry about which version of the link they have.

Potentially, the users upload to specified folder, which triggers the flow and moves the folder to the correct desired location with the desired permissions, then deletes the original location. You could even send an email with the link to the new folder (if desired).

Was this reply helpful? Yes No
adriennevh 27 on at

Like (0)

Report
Copy link

Link copied!

@DreamCatcher

The central drop box is an option for sure, but because we're dealing with external vendors, hoping their nomanclature will be consistent is going to be challenging.

I'll look into the Per Flow license. Currently I have a service account creating both the folder link and the file link, and it's not working properly.

@Pstork1

Unfortunately, we do require the link as it's going to be shared with external vendors who we dont want to require to have accounts, and we dont know which vendor it will be shared with. These are translaltion tickets, and our team has multiple vendors we use to get the jobs done.

Right now, i'm thinking of checking out the document instead of changing the permissions. I will set the folder to View/Edit and check out the file. This will functionally do the same, preventing edits, but allowing download and new documents to be added.

Was this reply helpful? Yes No