SOLVED

Lock file from being read by more than one user at a time

Iron Contributor

Note: I'm fully aware that this request might not make much sense, but...

 

Is it possible to lock a certain document library (or individual files for that matter) from being opened and read by more than one user simultanously?

 

In my case, it's pdf files. I'm basically looking for a way of checking-out and locking a file reading. If the pdf is opened already by someone; the next person trying to open it should preferably get a warning along the lines of "Sorry, this document is already being read by John Doe, and needs to be closed before you can read it."

4 Replies
best response confirmed by Tormod Solem Slupphaug (Iron Contributor)
Solution
Not possible out of box. You can check out for editing but not reading.

However. Just thinking out loud you could Probably craft a power automate flow to handle this. You would have to somehow get limited access for view files in directory and have a flow for granting access for x amount of time. Or two flows for check out and check in. And you have the flow only run and allow for an individual one at a time. So it could be done. But not out of box.

"Or two flows for check out and check in".

But would that, simply checking out a pdf, prevent others from reading it?

I meant a flow called that. You could name it whatever but it wouldn’t be a “check out”. The flow would be granting access to the file when the flow runs. Then after a period or time revoke that or have them check in flow to remove that permission.
I see :) Not sure if I got the experience needed to get something like this up and running, but thanks a lot for your replies :)
1 best response

Accepted Solutions
best response confirmed by Tormod Solem Slupphaug (Iron Contributor)
Solution
Not possible out of box. You can check out for editing but not reading.

However. Just thinking out loud you could Probably craft a power automate flow to handle this. You would have to somehow get limited access for view files in directory and have a flow for granting access for x amount of time. Or two flows for check out and check in. And you have the flow only run and allow for an individual one at a time. So it could be done. But not out of box.

View solution in original post